lchan release: always Deact SACCH
If an lchan is being released and had a SACCH active, there is no reason to
omit the Deact SACCH message ever. All of the callers that passed
do_deact_sacch = false did so for no good reason.
Drop the do_deact_sacch flag everywhere and, when the lchan type matches and
SAPI[0] is still active, simply always send a Deact SACCH message.
The do_deact_sacch flag was carried over from legacy code, by me, mainly
because I never really understood why it was there. I do hope I'm correct now,
asserting that having this flag makes no sense.
Change-Id: Id3301df059582da2377ef82feae554e94fa42035
diff --git a/tests/handover/handover_test.c b/tests/handover/handover_test.c
index 7cb4086..f728c5b 100644
--- a/tests/handover/handover_test.c
+++ b/tests/handover/handover_test.c
@@ -462,6 +462,8 @@
break;
case RSL_MT_IPAC_CRCX:
break;
+ case RSL_MT_DEACTIVATE_SACCH:
+ break;
default:
printf("unknown rsl message=0x%x\n", dh->c.msg_type);
}