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/.
Neels Hofmeyr gerrit-no-reply at lists.osmocom.orgPatch Set 1: Code-Review-1 (1 comment) I'm not sure I understand the max_trx. Which situation does it resolve? AFAIU a BTS simply has a given number of TRX by hardware, and a scenario may want to request a specific number of TRX (but I guess will generally not actually care how many there are). Who dictates a max there? If we have a max, why no min? Once we have a good explanation, that should go in the code somewhere and not be "hidden" in the commit log. https://gerrit.osmocom.org/#/c/8061/1//COMMIT_MSG Commit Message: Line 7: bts: Allow setting amounf of TRX and timeslot in cfg and from test at runtime amounf :) -- To view, visit https://gerrit.osmocom.org/8061 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I7f46eaf7a16f03268653299c93600c0443f691ac Gerrit-PatchSet: 1 Gerrit-Project: osmo-gsm-tester Gerrit-Branch: master Gerrit-Owner: Pau Espin Pedrol <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de> Gerrit-HasComments: Yes