Neels Hofmeyr has submitted this change and it was merged. ( 
https://gerrit.osmocom.org/12034 )

Change subject: cosmetic: drop some unused opaque struct defs
......................................................................

cosmetic: drop some unused opaque struct defs

Change-Id: I4d461dd39d0abdc4f2327445671459340ca1c946
---
M include/osmocom/msc/db.h
M include/osmocom/msc/iu_dummy.h
M src/libmsc/iu_dummy.c
3 files changed, 0 insertions(+), 5 deletions(-)

Approvals:
  Pau Espin Pedrol: Looks good to me, approved
  Vadim Yanitskiy: Looks good to me, but someone else must approve



diff --git a/include/osmocom/msc/db.h b/include/osmocom/msc/db.h
index a1de7d6..6d07055 100644
--- a/include/osmocom/msc/db.h
+++ b/include/osmocom/msc/db.h
@@ -24,10 +24,7 @@

 #include "gsm_subscriber.h"

-struct gsm_equipment;
 struct gsm_network;
-struct gsm_auth_info;
-struct gsm_auth_tuple;
 struct gsm_sms;

 /* one time initialisation */
diff --git a/include/osmocom/msc/iu_dummy.h b/include/osmocom/msc/iu_dummy.h
index d5e1428..01a8aa6 100644
--- a/include/osmocom/msc/iu_dummy.h
+++ b/include/osmocom/msc/iu_dummy.h
@@ -29,7 +29,6 @@
 #include <osmocom/core/linuxlist.h>

 struct msgb;
-struct gsm_auth_tuple;
 struct RANAP_Cause;
 struct osmo_auth_vector;

diff --git a/src/libmsc/iu_dummy.c b/src/libmsc/iu_dummy.c
index bb53367..3f11d94 100644
--- a/src/libmsc/iu_dummy.c
+++ b/src/libmsc/iu_dummy.c
@@ -34,7 +34,6 @@

 struct msgb;
 struct ranap_ue_conn_ctx;
-struct gsm_auth_tuple;
 struct RANAP_Cause;
 struct osmo_auth_vector;


--
To view, visit https://gerrit.osmocom.org/12034
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-MessageType: merged
Gerrit-Change-Id: I4d461dd39d0abdc4f2327445671459340ca1c946
Gerrit-Change-Number: 12034
Gerrit-PatchSet: 7
Gerrit-Owner: Neels Hofmeyr <[email protected]>
Gerrit-Reviewer: Jenkins Builder (1000002)
Gerrit-Reviewer: Pau Espin Pedrol <[email protected]>
Gerrit-Reviewer: Vadim Yanitskiy <[email protected]>

Reply via email to