This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
Harald Welte gerrit-no-reply at lists.osmocom.orgPatch Set 5: (1 comment) https://gerrit.osmocom.org/#/c/5705/5/include/osmocom/bsc/osmo_bsc_grace.h File include/osmocom/bsc/osmo_bsc_grace.h: Line 34: struct gsm_bts *bts); I think API-wise this might end up rather confusing. So either the BTS selection is done higher up the stack by the MSC/A interface and we know the BTS, or we hand down the LAC/CI and let the lower layers issue the request on as many BTSs as it wants. I guess what I would prefer is that we have the A interface related code that parses the cell identification list [eleemnts] and then we resolve the BTS or BTSs in one layer, and finally issue the paging on each bTS. So the 'bsc_grace_paging_request' would then basically *only* have a 'bts' parameter, and we would call that for as many BTS as we determine to be in the LAC/LAI/CIs specified by the MSC? Am I making sense? We can do this as multiple patches, and this could be the first one. I just think the APIs should become more obvious/clean, and less convoluted. -- To view, visit https://gerrit.osmocom.org/5705 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ic7772e75c3d7fb0df6e17e118bb33b3248352d4d Gerrit-PatchSet: 5 Gerrit-Project: osmo-bsc Gerrit-Branch: master Gerrit-Owner: Stefan Sperling <ssperling at sysmocom.de> Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org> Gerrit-Reviewer: Jenkins Builder Gerrit-HasComments: Yes