Vadim Yanitskiy has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/18591 )
Change subject: Do not mix public and private BTS features, use libosmocore's API ...................................................................... Patch Set 3: (3 comments) https://gerrit.osmocom.org/c/osmo-bts/+/18591/3/src/common/bts.c File src/common/bts.c: https://gerrit.osmocom.org/c/osmo-bts/+/18591/3/src/common/bts.c@261 PS3, Line 261: if (~trx->bts->flags & BTS_IMPL_FLAG_MS_PWR_CTRL_DSP) > I would really welcome a function helper for this, in order to: […] You're definitely trying to turn Osmocom into Helpercom ;) In any case, I will introduce a function to check if a flag is set. Setting a flag (bts->flags |= BTS_IMPL_FLAG_FOO) is super easy and clear, so it needs no API IMHO. https://gerrit.osmocom.org/c/osmo-bts/+/18591/3/src/common/oml.c File src/common/oml.c: https://gerrit.osmocom.org/c/osmo-bts/+/18591/3/src/common/oml.c@176 PS3, Line 176: msgb_tl16v_put(msg, NM_ATT_MANUF_ID, _NUM_BTS_FEAT/8 + 1, bts->features->data); > isn't there an API to get the data pointer? API for 'foo->data'? Is it really something that requires API? https://gerrit.osmocom.org/c/osmo-bts/+/18591/3/src/common/vty.c File src/common/vty.c: https://gerrit.osmocom.org/c/osmo-bts/+/18591/3/src/common/vty.c@845 PS3, Line 845: for (i = 0, no_features = true; i < sizeof(bts->flags) * 8; i++) { > features = false, then setting it to true and checking if (!features) is > easier to understand :) This is unrelated. I am (re)using the existing variable with its original name. -- To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/18591 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit-Change-Id: Icf792d02323bb73e3b8d46384c7890cb1eb4731e Gerrit-Change-Number: 18591 Gerrit-PatchSet: 3 Gerrit-Owner: Vadim Yanitskiy <vyanits...@sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Vadim Yanitskiy <vyanits...@sysmocom.de> Gerrit-Reviewer: laforge <lafo...@osmocom.org> Gerrit-Reviewer: pespin <pes...@sysmocom.de> Gerrit-Comment-Date: Tue, 02 Jun 2020 10:41:27 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: pespin <pes...@sysmocom.de> Gerrit-MessageType: comment
