Attention is currently required from: fixeria, laforge, pespin. falconia has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hlr/+/34448?usp=email )
Change subject: SMS over GSUP: implement vty config of SMSC routing ...................................................................... Patch Set 2: (1 comment) File include/osmocom/hlr/hlr_sms.h: https://gerrit.osmocom.org/c/osmo-hlr/+/34448/comment/db52a7d7_b6671ad9 PS2, Line 17: void smsc_del(struct hlr_smsc *smsc); > Regarding "adding object to llist during alloc", I think it makes sense to do > so and it's useful/sim […] @laforge says that alloc+del is inconsistent, instead it should be either alloc+free or add+del - and I agree. In the present case of HLR configs for EUSE/USSD and SMSC entities and routing, it looks like I need to do the following sequence: 1) mark the present patch as WIP; 2) prepare a separate patch changing the existing EUSE/USSD code to the agreed-upon convention, and get that patch through review to merge; 3) revisit the present patch and make it the same as the newly fixed EUSE/USSD. What I need now is an agreement from @laforge and @pespin on which convention I should use in the present cases of EUSE/USSD and SMSC: alloc+free or add+del? -- To view, visit https://gerrit.osmocom.org/c/osmo-hlr/+/34448?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-hlr Gerrit-Branch: master Gerrit-Change-Id: I1624dcd9d22b4efca965ccdd1c74f0063a94a33c Gerrit-Change-Number: 34448 Gerrit-PatchSet: 2 Gerrit-Owner: falconia <[email protected]> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <[email protected]> Gerrit-CC: laforge <[email protected]> Gerrit-CC: pespin <[email protected]> Gerrit-Attention: laforge <[email protected]> Gerrit-Attention: pespin <[email protected]> Gerrit-Attention: fixeria <[email protected]> Gerrit-Comment-Date: Tue, 19 Sep 2023 17:32:44 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: falconia <[email protected]> Comment-In-Reply-To: laforge <[email protected]> Comment-In-Reply-To: pespin <[email protected]> Comment-In-Reply-To: fixeria <[email protected]> Gerrit-MessageType: comment
