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/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "UNNAMED PROJECT". The branch, sysmocom/revert_WAIT_ASSIGN has been updated discards 8a5a33aa686e567cde18f5841fb4cdd0d73e53e6 (commit) via a4fd319f8408946a9b5824c8cd081be92527e6d6 (commit) via 7fd177b91c5b0cb32078d87b41da5ad38c2f08ad (commit) via 2d91260ea436c06058ae25501dbbf2b9b29e7ed4 (commit) via 6bae2d11f1c6801c2f2ef9d6b1bd7b471767fc3c (commit) via 0b4da058ad45984904c6860ec3820b213c683cce (commit) via 79cb2451576ff07fa65a819f605c82e732120e4c (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (8a5a33aa686e567cde18f5841fb4cdd0d73e53e6) \ N -- N -- N (a4fd319f8408946a9b5824c8cd081be92527e6d6) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-pcu/commit/?id=a4fd319f8408946a9b5824c8cd081be92527e6d6 commit a4fd319f8408946a9b5824c8cd081be92527e6d6 Author: Neels Hofmeyr <neels at hofmeyr.de> Date: Wed Jun 8 15:27:40 2016 +0200 Revert "tbf: Add state WAIT_ASSIGN" This reverts commit f1a7b8fc6651f92a8b7f3f27b7ca05d07f4e44e0. Conflicts: tests/tbf/TbfTest.err The commit broke GPRS service at least for osmo-bts-sysmo on a SysmoBTS 1002 with current master of osmo-bts (ef30f50d5d6d5f863fc147d05ccdceb89284934e). The error observed is the following log output (was viewing both osmo-bts-sysmo and osmo-pcu logs interleaved): <0002> tbf.cpp:874 TBF(TFI=0 TLLI=0x00000000 DIR=UL STATE=WAIT ASSIGN) T3169 timeout during transsmission <0002> tbf.cpp:893 - Assignment was on CCCH <0002> tbf.cpp:899 - No uplink data received yet <0007> l1sap.c:904 RACH for packet access <0001> pcu_l1_if.cpp:311 RACH request received: sapi=1 qta=0, ra=121, fn=13653 [repeat] When removing this single commit from current osmo-pcu master, GPRS service works well on SysmoBTS, with current osmo-bts master. The TbfTest.err expected output needed adjustment after the revert. Disclaimer: I am not aware of adverse effects this commit may have. I have no idea what the WAIT_ASSIGN state is used for -- further review is required. Change-Id: I1532f8e93194368cdc1e3846f82afa6d68cd5fbd ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 91 ++++++++++++++++++++++++------------ src/osmo-bts-litecell15/lc15_l1_if.c | 2 +- 2 files changed, 63 insertions(+), 30 deletions(-) hooks/post-receive -- UNNAMED PROJECT