This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
lynxis lazus gerrit-no-reply at lists.osmocom.orglynxis lazus has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/25559 ) Change subject: ns2: trigger a reset in case of receiving a NS STATUS with incompatible protocol state ...................................................................... Patch Set 1: Code-Review-1 I'm uncertain about this commit. keeping it in WIP and gerrit for later. I'm unsure if we should trigger a reset here. Maybe parsing the PDU as far as possible to know if it's UNITDATA (to ignore) or not and to decide if a reset is correct. -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/25559 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I912315f816bd0597d4646627dbfdd270fbae2509 Gerrit-Change-Number: 25559 Gerrit-PatchSet: 1 Gerrit-Owner: lynxis lazus <lynxis at fe80.eu> Gerrit-Reviewer: lynxis lazus <lynxis at fe80.eu> Gerrit-CC: Jenkins Builder Gerrit-Comment-Date: Thu, 23 Sep 2021 11:42:21 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20210923/464b95b8/attachment.htm>