Attention is currently required from: neels.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-sccp/+/32214 )
Change subject: add two value_string[]s related to N-PCSTATE
......................................................................
Patch Set 1: Code-Review+1
--
To view, visit https://gerrit.osmocom.org/c/libosmo-sccp/+/32214
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-sccp
Gerrit-Branch: master
Gerrit-Change-Id: I873ea30e8f64280487769668c748c67ce4ff4023
Gerrit-Change-Number: 32214
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 05 Apr 2023 07:23:12 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/32151 )
Change subject: SCCP N-PCSTATE: trigger MSC status on PC availability
......................................................................
Patch Set 2:
This change is ready for review.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/32151
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: I3a0869598b8395601a16d78dbc46eec400c0ea84
Gerrit-Change-Number: 32151
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Wed, 05 Apr 2023 05:40:28 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: neels.
Hello Jenkins Builder, laforge,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/osmo-bsc/+/32152
to look at the new patch set (#2).
Change subject: log: N-PCSTATE: use new value_strings
......................................................................
log: N-PCSTATE: use new value_strings
Related: SYS#6319
Depends: I873ea30e8f64280487769668c748c67ce4ff4023 (libosmo-sccp)
Change-Id: I7a13fcf2bfee232c6cebc3c1180b956a73abc24e
---
M src/osmo-bsc/osmo_bsc_sigtran.c
1 file changed, 22 insertions(+), 6 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-bsc refs/changes/52/32152/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/32152
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: I7a13fcf2bfee232c6cebc3c1180b956a73abc24e
Gerrit-Change-Number: 32152
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: pespin.
falconia has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/32197 )
Change subject: include/osmocom/gsm/protocol: add gsm_06_31.h
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
Let's see if we can all get on the same page here: my end objective in this patch series is to add some new functions to libosmocodec, and these functions happen to have this 06.31-defined ternary enum as their return value. Harald just said that naming ETSI-defined or 3GPP-defined things without osmo_ prefix is fine in <osmocom/gsm/protocol/xxx.h> headers - but if the present patch were to be accepted, then the very next patch in the series will have <osmocom/codec/codec.h> including the new <osmocom/gsm/protocol/gsm_06_31.h> header, in order to get that enum for the return value of osmo_{fr,efr}_sid_classify() functions. Thus if namespace pollution is a concern, then it does not stay confined to programs that explicitly include <osmocom/gsm/protocol/gsm_06_31.h>, instead everyone who includes <osmocom/codec/codec.h> will get it too.
So what should we do? Continue with the approach of creating this new <osmocom/gsm/protocol/gsm_06_31.h> header to hold the GSM 06.31 SID class enum, or go back to my original approach of putting this enum directly into <osmocom/codec/codec.h>? And as for the enum itself and its items, should I just bite the bullet and prefix them all with osmo_ even though they aren't Osmo-defined? If we decide the latter, I suggest this naming:
enum osmo_gsm631_sid_class
OSMO_GSM631_SID_CLASS_SPEECH
OSMO_GSM631_SID_CLASS_INVALID
OSMO_GSM631_SID_CLASS_VALID
Disadvantage: long. Advantage: achieves namespace containment while also making it clear that the definitions come from the spec and are not Osmocom-invented.
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/32197
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: If004b668778d3d9cf6cd998b3af2dbfa83691529
Gerrit-Change-Number: 32197
Gerrit-PatchSet: 1
Gerrit-Owner: falconia <falcon(a)freecalypso.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 04 Apr 2023 20:43:11 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment