aboutsummaryrefslogtreecommitdiffstats
path: root/src/ranap/RANAP_MBMSRABReleaseRequest.h
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2015-12-16 17:26:05 +0100
committerHarald Welte <laforge@gnumonks.org>2015-12-16 17:26:05 +0100
commit49695572ba3c55c012c9b1a55d13cfca18f4ebbf (patch)
treedde5fb23a6e3bae35e71b0df2edbacf0aa5d6557 /src/ranap/RANAP_MBMSRABReleaseRequest.h
parenta0c74240fa6457d77bc367284760fe2240ec1f5f (diff)
One further RANAP hacking session
This is not development, it is random trial and error hacking. I really hate the fact that we have no useful asn.1 code generator and need to work with hacks like asn1tostruct.py and asn1c without information object classes :/ This commit is a one-day-long iteration of trial+error, manually editing and adding the .asn source of RANAP until we get something that in the end at least compiles and links. Do I trust the resulting code? No. But we have no alternative :(
Diffstat (limited to 'src/ranap/RANAP_MBMSRABReleaseRequest.h')
-rw-r--r--src/ranap/RANAP_MBMSRABReleaseRequest.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/ranap/RANAP_MBMSRABReleaseRequest.h b/src/ranap/RANAP_MBMSRABReleaseRequest.h
index 6f9d34a..e033d39 100644
--- a/src/ranap/RANAP_MBMSRABReleaseRequest.h
+++ b/src/ranap/RANAP_MBMSRABReleaseRequest.h
@@ -22,12 +22,12 @@ extern "C" {
/* RANAP_MBMSRABReleaseRequest */
typedef struct RANAP_MBMSRABReleaseRequest {
- struct mBMSRABReleaseRequest_ies {
+ struct mbmsrabReleaseRequest_ies {
A_SEQUENCE_OF(RANAP_IE_t) list;
/* Context for parsing across buffer boundaries */
asn_struct_ctx_t _asn_ctx;
- } mBMSRABReleaseRequest_ies;
+ } mbmsrabReleaseRequest_ies;
/*
* This type is extensible,
* possible extensions are below.