tree ec73d9f7fd59ad594573e9def7e8a7b5c7687bcf
parent d30922f7a384947f6766523180cad7b108c9d751
author Neels Hofmeyr <neels@hofmeyr.de> 1541539447 +0100
committer Neels Hofmeyr <nhofmeyr@sysmocom.de> 1542212190 +0000

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