Attention is currently required from: pespin.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/32212 )
Change subject: NM: NACK received OML OPSTART if no attributes were set beforehand
......................................................................
Patch Set 2:
(2 comments)
File src/common/nm_bb_transc_fsm.c:
https://gerrit.osmocom.org/c/osmo-bts/+/32212/comment/ff12f4a9_89c55d05
PS2, Line 139: SITE_MGR
You meant BASEBAND TRANSCEIVER here?
Are there any attributes for it in the OML spec?
I see none in section 6.5, so IMO this code chunk will always remain no-op.
File src/common/nm_bts_sm_fsm.c:
https://gerrit.osmocom.org/c/osmo-bts/+/32212/comment/170263e8_299d87c6
PS2, Line 103: SITE_MGR
Are there any attributes for it in the OML spec?
I see none in section 6.5, so IMO this code chunk will always remain no-op.
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/32212
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: I771ecc2f60873a3549e8a07a2e57c7948dfc993e
Gerrit-Change-Number: 32212
Gerrit-PatchSet: 2
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: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 05 Apr 2023 07:56:12 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: pespin.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/32209 )
Change subject: lc15,oc2g,sysmo: Update GPRS NM object state at the right time
......................................................................
Patch Set 2: Code-Review+2
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/32209
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: I2f331954835496504f1fafa572bd46ee83b03a63
Gerrit-Change-Number: 32209
Gerrit-PatchSet: 2
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: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 05 Apr 2023 07:48:50 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment
Attention is currently required from: pespin.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/32196 )
Change subject: nm: Drop NM_EV_SETATTR_{ACK/NACK}
......................................................................
Patch Set 3:
(4 comments)
File src/osmo-bts-lc15/oml.c:
https://gerrit.osmocom.org/c/osmo-bts/+/32196/comment/7a1430ad_a349709d
PS3, Line 1851: rc = 0;
This is weird. Why not simply `return 0` down below?
https://gerrit.osmocom.org/c/osmo-bts/+/32196/comment/1d29845b_f3a0fa77
PS3, Line 1854: rc = 0;
So it's fine if we get an unknown/unhandled `foh->msg_type` value?
File src/osmo-bts-sysmo/oml.c:
https://gerrit.osmocom.org/c/osmo-bts/+/32196/comment/96cb51f2_a1ce52c8
PS3, Line 1726: case NM_MT_SET_RADIO_ATTR:
`rc` is uninitialized in this case. I suggest removing it and simply doing `return 0` below.
File src/osmo-bts-virtual/bts_model.c:
https://gerrit.osmocom.org/c/osmo-bts/+/32196/comment/91e6280f_c4898f67
PS3, Line 148: rc = 0;
Are you sure 0 is the right value here? Not `-ENOTSUP`?
--
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/32196
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: I281c07bb5ad88ee03542f092141cebe036d10aee
Gerrit-Change-Number: 32196
Gerrit-PatchSet: 3
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: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Wed, 05 Apr 2023 07:44:50 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment