https://osmocom.org/https://osmocom.org/favicon.ico?16647414092020-11-29T16:50:09ZOpen Source Mobile Communicationsosmo-gbproxy - Bug #4876: proper naming / identification of NS-VC FSMshttps://osmocom.org/issues/4876?journal_id=204562020-11-29T16:50:09Zlaforge
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> changed from <i>lynxis</i> to <i>laforge</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Urgent</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>90</i></li></ul><p><a class="external" href="https://gerrit.osmocom.org/c/libosmocore/+/21400">https://gerrit.osmocom.org/c/libosmocore/+/21400</a></p> osmo-gbproxy - Bug #4876: proper naming / identification of NS-VC FSMshttps://osmocom.org/issues/4876?journal_id=204572020-11-29T16:58:56Zlaforge
<ul></ul><pre>
<0024> gprs_ns2_vc_fsm.c:692 GPRS-NS2-VC(FR-hdlcnet1-DLCI16-NSEI1-NSVCI1)[0x6120000018a0]{BLOCKED}: Received Event UNBLOCK_ACK
<0024> gprs_ns2_vc_fsm.c:306 GPRS-NS2-VC(FR-hdlcnet1-DLCI16-NSEI1-NSVCI1)[0x6120000018a0]{BLOCKED}: state_chg to UNBLOCKED
</pre> osmo-gbproxy - Bug #4876: proper naming / identification of NS-VC FSMshttps://osmocom.org/issues/4876?journal_id=205152020-12-02T23:02:41Zlaforge
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Stalled</i></li></ul> osmo-gbproxy - Bug #4876: proper naming / identification of NS-VC FSMshttps://osmocom.org/issues/4876?journal_id=208442021-01-17T19:29:20Zlaforge
<ul><li><strong>Status</strong> changed from <i>Stalled</i> to <i>Feedback</i></li></ul><p>remaining FIXME in patch has been addressed; patch is waiting for review.</p> osmo-gbproxy - Bug #4876: proper naming / identification of NS-VC FSMshttps://osmocom.org/issues/4876?journal_id=217992021-03-29T21:25:40Zlaforge
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>90</i> to <i>100</i></li></ul><p>patch was merged 2 months ago.</p>