diff options
author | Neels Hofmeyr <neels@hofmeyr.de> | 2018-12-07 14:47:34 +0100 |
---|---|---|
committer | Neels Hofmeyr <neels@hofmeyr.de> | 2018-12-07 15:04:33 +0100 |
commit | 4e0dd536b4e6634eb9d54c76f478766a90c21b4c (patch) | |
tree | cafd3ea871d93c761e301392ab4e726997e9b650 /src | |
parent | 65a8daadfd3755c8fbe56f879d96fe056fa274bb (diff) |
ASS-COMPL: do not fire Sec Mode Compl event
BSSMAP Assignment Complete:
Do not invoke ran_conn_rx_sec_mode_compl(), that's just weird.
Instead this should call msc_assign_compl(), which is currently dead code and
does nothing ... and there are some more strings attached, being resolved in a
subsequent patch.
Change-Id: I448fdb783364628005437b3d866d1a076a9767d7
Diffstat (limited to 'src')
-rw-r--r-- | src/libmsc/a_iface_bssap.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/src/libmsc/a_iface_bssap.c b/src/libmsc/a_iface_bssap.c index a10bd4296..d84a2346b 100644 --- a/src/libmsc/a_iface_bssap.c +++ b/src/libmsc/a_iface_bssap.c @@ -579,10 +579,6 @@ static int bssmap_rx_ass_compl(struct ran_conn *conn, struct msgb *msg, return -EINVAL; } - /* FIXME: Seems to be related to authentication or, - encryption. Is this really in the right place? */ - ran_conn_rx_sec_mode_compl(conn); - return 0; } |