Change in osmo-bsc[master]: add fixme comment for vty 'interference-meas level-bounds'

neels gerrit-no-reply at lists.osmocom.org
Sun Jul 11 18:55:04 UTC 2021


neels has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bsc/+/24886 )

Change subject: add fixme comment for vty 'interference-meas level-bounds'
......................................................................


Patch Set 3:

(1 comment)

https://gerrit.osmocom.org/c/osmo-bsc/+/24886/3/src/osmo-bsc/bsc_vty.c 
File src/osmo-bsc/bsc_vty.c:

https://gerrit.osmocom.org/c/osmo-bsc/+/24886/3/src/osmo-bsc/bsc_vty.c@5048 
PS3, Line 5048: 	 
> Ack
the point is not that we need 'drop oml' (which is correctly indicated by that VTY attribute).
The point is that as soon as the user changes the bsc's config, the incoming reported interference levels will be interpreted wrongly. i see it as a full out bug.

if we agree on the next patch that fixes the issue, we can also squash this change away.



-- 
To view, visit https://gerrit.osmocom.org/c/osmo-bsc/+/24886
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: I501e07d34a26a1571a244f643563b5bf985c59d4
Gerrit-Change-Number: 24886
Gerrit-PatchSet: 3
Gerrit-Owner: neels <nhofmeyr at sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy at sysmocom.de>
Gerrit-Reviewer: pespin <pespin at sysmocom.de>
Gerrit-CC: laforge <laforge at osmocom.org>
Gerrit-Comment-Date: Sun, 11 Jul 2021 18:55:04 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge at osmocom.org>
Comment-In-Reply-To: fixeria <vyanitskiy at sysmocom.de>
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20210711/f32fcc4b/attachment.htm>


More information about the gerrit-log mailing list