Attention is currently required from: keith. fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-msc/+/31131 ) Change subject: LCLS: Fix Global Call Reference generation ...................................................................... Patch Set 2: Code-Review+2 (2 comments) File src/libmsc/transaction.c: https://gerrit.osmocom.org/c/osmo-msc/+/31131/comment/e2e7b300_1896c65e PS1, Line 165: 0x%x
I'm guessing you mean 0x%04x, although I don't understand why. […] If let's say callref is 1, then '0x%x' would render '0x1', '0x%04x' would render '0x00000001'. By using '0x%04x' you ensure consistent formatting, regardless of the callref value. Now I remember that callref always has some MSB octet set, e.g. 0x[80]000001, so even with '0x%x' it would always be '0xXXXXXXXX'...
https://gerrit.osmocom.org/c/osmo-msc/+/31131/comment/767270f6_93fe7268 PS1, Line 165: %sfor
Actually done intentionally, because osmo_hexdump() seems to add a space at the end. […] Ack
-- To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/31131 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-msc Gerrit-Branch: master Gerrit-Change-Id: I9c33a89c819e8925d89ca833d7705ed5ced6b566 Gerrit-Change-Number: 31131 Gerrit-PatchSet: 2 Gerrit-Owner: keith <keith@rhizomatica.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy@sysmocom.de> Gerrit-Reviewer: laforge <laforge@osmocom.org> Gerrit-Attention: keith <keith@rhizomatica.org> Gerrit-Comment-Date: Wed, 01 Feb 2023 10:45:25 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: Yes Comment-In-Reply-To: fixeria <vyanitskiy@sysmocom.de> Comment-In-Reply-To: keith <keith@rhizomatica.org> Gerrit-MessageType: comment