Attention is currently required from: fixeria.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-sip-connector/+/29561 )
Change subject: mncc: fix MNCC_SETUP_REQ: set MNCC_F_GCR if GCR is present
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
Haven't i seen this patch already somewhere else?
--
To view, visit https://gerrit.osmocom.org/c/osmo-sip-connector/+/29561
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-sip-connector
Gerrit-Branch: master
Gerrit-Change-Id: I9dd22caef78e37543dac8a6b31a6ee349e7e5aa8
Gerrit-Change-Number: 29561
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 03 Oct 2022 09:21:25 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
fixeria has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-msc/+/29562 )
Change subject: mncc: move MNCC_F_ALL from mncc.c to mncc.h
......................................................................
mncc: move MNCC_F_ALL from mncc.c to mncc.h
Move it closer to the other MNCC_F_* entries, so that it's more
likely that it gets updated when new flags are added.
Change-Id: If1a12a696b87184c9eee14f475594c317927427b
Related: OS#5282
---
M include/osmocom/msc/mncc.h
M src/libmsc/mncc.c
2 files changed, 3 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-msc refs/changes/62/29562/1
diff --git a/include/osmocom/msc/mncc.h b/include/osmocom/msc/mncc.h
index 06a5dcc..8a1e4ad 100644
--- a/include/osmocom/msc/mncc.h
+++ b/include/osmocom/msc/mncc.h
@@ -126,6 +126,9 @@
#define MNCC_F_SIGNAL 0x2000
#define MNCC_F_GCR 0x4000
+/* UPDATEME when adding new MNCC_F_* entries above */
+#define MNCC_F_ALL 0x7fff
+
struct gsm_mncc {
/* context based information */
uint32_t msg_type;
diff --git a/src/libmsc/mncc.c b/src/libmsc/mncc.c
index f446f98..24e79a7 100644
--- a/src/libmsc/mncc.c
+++ b/src/libmsc/mncc.c
@@ -110,8 +110,6 @@
* MNCC validation code. Move to libosmocore once headers are merged
************************************************************************/
-#define MNCC_F_ALL 0x7fff
-
static int check_string_terminated(const char *str, unsigned int size)
{
int i;
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/29562
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: If1a12a696b87184c9eee14f475594c317927427b
Gerrit-Change-Number: 29562
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: newchange
Attention is currently required from: keith.
fixeria has uploaded a new patch set (#2) to the change originally created by keith. ( https://gerrit.osmocom.org/c/osmo-msc/+/29559 )
Change subject: Update MNCC field validation mask.
......................................................................
Update MNCC field validation mask.
In c6921e5068ba62cde67707fb3c8103919d1e0c0e, 0x4000 was added to the
possible MNCC field flags, but before this commit, using it would
result in an ERROR of "Unknown MNCC field mask 0x....."
Related: OS#5282
Change-Id: I9e7d224e7f2d6d2824b2466752b6e8c994ac5a3d
---
M src/libmsc/mncc.c
1 file changed, 1 insertion(+), 1 deletion(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-msc refs/changes/59/29559/2
--
To view, visit https://gerrit.osmocom.org/c/osmo-msc/+/29559
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Change-Id: I9e7d224e7f2d6d2824b2466752b6e8c994ac5a3d
Gerrit-Change-Number: 29559
Gerrit-PatchSet: 2
Gerrit-Owner: keith <keith(a)rhizomatica.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: keith <keith(a)rhizomatica.org>
Gerrit-MessageType: newpatchset
Attention is currently required from: fixeria.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-netif/+/29528 )
Change subject: osmux: Allocate struct osmux_out_handle through API
......................................................................
Patch Set 1:
(1 comment)
File src/osmux_input.c:
https://gerrit.osmocom.org/c/libosmo-netif/+/29528/comment/c8102dcf_c92558ef
PS1, Line 737: /* DEPRECATED: Use talloc_free() instead (will call osmux_xfrm_input_talloc_destructor()) */
> What are the benefits of using a talloc destructor? If I allocate something with talloc, then yes, I […]
I chose to use a talloc destructor because it makes it easier to destroy the object when the parent object is destroy and make sure stuff is not left around. This is useful for existing users to transition to the new talloc allocated API, since they don't need necessarily to care about finding out where to destroy the object in the existing code.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-netif/+/29528
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-netif
Gerrit-Branch: master
Gerrit-Change-Id: I752ab031f935f04731bb1a354333f1682a1aa5bd
Gerrit-Change-Number: 29528
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 03 Oct 2022 09:19:52 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-MessageType: comment
Attention is currently required from: fixeria.
pespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/29551 )
Change subject: vty: 'hopping arfcn add': succeed if adding arfcn already in set
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
> Who reads those warnings?
I did in order to find out what the issue was.
> I am not really sure if blindly appending hopping ARFCNs is correct. Imagine an operator wants to configure a new set. I think the existing set must be cleaned first, otherwise you may end up having a mix of old and new ARFCNs.
This is really an orthogonal discussion and it's up to the user/customer to decide how do they want to do it, aka if they need a clear command or not.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/29551
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: Ia4e70d20d48a28c46a21dd10358577e5c798744c
Gerrit-Change-Number: 29551
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 03 Oct 2022 09:15:08 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Gerrit-MessageType: comment