laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmocom-bb/+/28110 )

Change subject: trxcon: clarify L1CTL_DM_REL_REQ related logging ......................................................................

trxcon: clarify L1CTL_DM_REL_REQ related logging

In reality, trxcon does not switch back to BCCH itself. Neither the firmware does, so let's correct this confusing log message.

Change-Id: Iad308ad980af4caa7d7d1b358ba7288885f96e04 --- M src/host/trxcon/l1ctl.c 1 file changed, 1 insertion(+), 2 deletions(-)

Approvals: Jenkins Builder: Verified laforge: Looks good to me, approved

diff --git a/src/host/trxcon/l1ctl.c b/src/host/trxcon/l1ctl.c index 95ba9b6..94a4d18 100644 --- a/src/host/trxcon/l1ctl.c +++ b/src/host/trxcon/l1ctl.c @@ -687,8 +687,7 @@

static int l1ctl_rx_dm_rel_req(struct l1ctl_link *l1l, struct msgb *msg) { - LOGP(DL1C, LOGL_NOTICE, "Received L1CTL_DM_REL_REQ, " - "switching back to CCCH\n"); + LOGP(DL1C, LOGL_NOTICE, "Received L1CTL_DM_REL_REQ, resetting scheduler\n");

/* Reset scheduler */ sched_trx_reset(l1l->trx, false);