Attention is currently required from: laforge, pespin, keith. dexter has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-abis/+/32374 )
Change subject: e1d: reconnect to osmo-e1d after connection loss ...................................................................... Patch Set 6: (1 comment) File src/input/e1d.c: https://gerrit.osmocom.org/c/libosmo-abis/+/32374/comment/045db258_dc82a082 PS4, Line 123: if (bfd->list.next && bfd->list.next != LLIST_POISON1) > no answer on this? I'd welcome if you checked my comments more carefully > before submitting new versi […] I always go through the whole patchset, fix all comments and then I push. I guess that is why sometimes comments slip through, but this is patchset 6 and the comment is from patchset 4 - i don't know. The line if (bfd->list.next && bfd->list.next != LLIST_POISON1) can be found in many locations. I wonder why osmo_fd_unregister() does not do a osmo_fd_is_registered() internally. We should fix this in libosmocore first and then remove those checks here. Does this make sense? -- To view, visit https://gerrit.osmocom.org/c/libosmo-abis/+/32374 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmo-abis Gerrit-Branch: master Gerrit-Change-Id: Iaf4d42c2f009b1d7666e319fabdeb2598aa0b338 Gerrit-Change-Number: 32374 Gerrit-PatchSet: 6 Gerrit-Owner: dexter <[email protected]> Gerrit-Reviewer: Jenkins Builder Gerrit-CC: keith <[email protected]> Gerrit-CC: laforge <[email protected]> Gerrit-CC: pespin <[email protected]> Gerrit-CC: tnt <[email protected]> Gerrit-Attention: laforge <[email protected]> Gerrit-Attention: pespin <[email protected]> Gerrit-Attention: keith <[email protected]> Gerrit-Comment-Date: Wed, 26 Apr 2023 12:21:05 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: pespin <[email protected]> Gerrit-MessageType: comment
