osmocom-commitlog

osmocom-commitlog@lists.osmocom.org

7948 discussions

osmo-python-tests.git branch master updated. c35bb473e449ec8b0d6e6ab64196331e89efef95

by gitosis＠osmocom.org

This 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, master has been updated via c35bb473e449ec8b0d6e6ab64196331e89efef95 (commit) from 7f7c4b441027ff64bddafe2a378e0d1a72f8b285 (commit) 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/python/osmo-python-tests/commit/?id=c35bb473e449ec8… commit c35bb473e449ec8b0d6e6ab64196331e89efef95 Author: Max <msuraev(a)sysmocom.de> Date: Fri Dec 15 11:56:05 2017 +0100 Expand CI tests * make sure jenkins.sh fails on any errors similar to other jenkins jobs * always explicitly use python2 instead of generic python * add basic module import tests for python 2 and 3 * add comments Change-Id: I0f4639537d227c513859d4552533ce1e41df9deb ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 11 ++++++++++- tests/test_py2.py | 7 +++++++ tests/test_py3.py | 7 +++++++ 3 files changed, 24 insertions(+), 1 deletion(-) create mode 100644 tests/test_py2.py create mode 100644 tests/test_py3.py hooks/post-receive -- UNNAMED PROJECT

7 years, 6 months

libosmocore.git branch neels/ctrl_parsing updated. 0.10.2-71-ge554429d

by gitosis＠osmocom.org

7 years, 6 months

libosmocore.git branch neels/ctrl_parsing updated. 0.10.2-72-g41dcec81

by gitosis＠osmocom.org

This 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 "An utility library for Open Source Mobile Communications". The branch, neels/ctrl_parsing has been updated discards 179f3a01446556d0d8eeb816c0c2b68034495180 (commit) discards c16258365ea80c9d35558e38eaa7f482eb357f24 (commit) discards e56600fa42e0a229a1a5bcf95fc8d3b9a4c053ac (commit) discards b61510abaeec814dfdf6f33ff5534c6ac1d6020f (commit) discards 4602cbff6231d7c106b880c5a4f45c2fca6e640f (commit) discards 0e759be493086f13ad476e08e5ba4c70b5a2c689 (commit) discards 4dbc6fca9a177941af2a3d3f8e3cabfb0825e80d (commit) discards 62feb5389c06f9fec19d21ba623195c59a2864cd (commit) discards 414901b2cd688783f56fced6311d5d7abfaaa98f (commit) discards 976214df85b004310ab49708d9170a1f5d14a039 (commit) discards 7fe60fe3d0576adbbd82919f43cfbb431a8d0c6a (commit) discards 65caf44d917c3bfa6c7fa2269aaa81d94981aad4 (commit) discards 62cc9bfee0c1cf30647d7f97261cc02519c797e9 (commit) via 41dcec816eb56d69dc69120e6bac06365d783a0a (commit) via e554429d04bceaac626165d13b69948477482e06 (commit) via ff1713e115789f1fff7f6fdc7f34b321fab27064 (commit) via c4eaafd6a195491d93161b165ecd7af5456267d5 (commit) via 29ed24daee0351f5bd1947a74d0a7c40fdf96d7f (commit) via 41eec760c14a594042daab768e85e4a04d20dfc4 (commit) via 6115231b49382c6b21677c8ec985f61af93383c3 (commit) via 3ddb493599b61fcbe7dddb29ab6ed3a13914648c (commit) via 86f9b1902cb0294a2b3c096dce88a15439d1d661 (commit) via 32c8f8ac9999a0fa0791a7ef1bdd87210876e15f (commit) via d8ad45804a605d9c0f22725aecf9a38450a35e31 (commit) via 5674c182b620bd7cb2c5a175382f8e72cecea1cf (commit) via 937ddea6cce45f3f6dcb8177ea86162f15ecb5f9 (commit) via e5a2bdbc5501b892605a6a1fe7e30fb2f1546d42 (commit) via 3ef14a241afc123560e9a50d17948b040481b299 (commit) via 62e40855c2b1b50627dba5b187be8869e2cb2054 (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 (179f3a01446556d0d8eeb816c0c2b68034495180) \ N -- N -- N (41dcec816eb56d69dc69120e6bac06365d783a0a) 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/libosmocore/commit/?id=41dcec816eb56d69dc69120e6bac… commit 41dcec816eb56d69dc69120e6bac06365d783a0a Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Mon Dec 18 03:12:01 2017 +0100 add osmo_auth_c3(): separate from gsm_milenage() To send a Ciphering Mode Command, we may need to derive a Kc from UMTS AKA tokens. gsm_milenage() derives Kc from 3G tokens, but also derives an SRES. For SRES, it requires an OPC, which may need to be derived from OP first. All we need is a Kc, so we could feed a zero OPC ... but to simplify the function call for cases where just a Kc is required, separate the c3 function out from gsm_milenage(), as osmo_auth_c3(). Obviously call osmo_auth_c3() from gsm_milenage() (meaning that osmo-hlr's 55.205 derived auc tests still cover exactly that implementation). Prepares: If04e405426c55a81341747a9b450a69188525d5c (osmo-msc) Related: OS#2745 Change-Id: I85a1d6ae95ad9e5ce9524ef7fc06414848afc2aa http://cgit.osmocom.org/libosmocore/commit/?id=e554429d04bceaac626165d13b69… commit e554429d04bceaac626165d13b69948477482e06 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 01:18:53 2017 +0100 ctrl: separate handling of GET_REPLY, SET_REPLY and TRAP So far, error reporting just says "Trap/Reply", more accurately report 'GET REPLY', 'SET REPLY' and 'TRAP' as appropriate. Change-Id: Ic25a251502499aeda4e2952ec4190a1fa0bebb01 http://cgit.osmocom.org/libosmocore/commit/?id=ff1713e115789f1fff7f6fdc7f34… commit ff1713e115789f1fff7f6fdc7f34b321fab27064 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Tue Sep 26 14:21:44 2017 +0200 ctrl: tighten CTRL input parsing Validate that incoming CTRL commands... - have decimal IDs, - return error on trailing characters, - have invalid characters in variable identifiers, - send detailed error messages as reply to the requestor. Adjust ctrl_test.{c,ok}, which best show the change in behavior. Message handling causes log messages on stderr; previously, stderr was empty. Add '[ignore]' in testsuite.at so that the nonempty stderr doesn't cause test failures. Change-Id: I96a9b6b6a3a5e0b80513aa9eaa727ae8c9c7d7a1 http://cgit.osmocom.org/libosmocore/commit/?id=c4eaafd6a195491d93161b165ecd… commit c4eaafd6a195491d93161b165ecd7af5456267d5 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 01:12:35 2017 +0100 ctrl: on parse errors, return a detailed message to sender The recently added ctrl_cmd_parse2() returns non-NULL cmd with error messages upon parsing errors. In handle_control_read(), use ctrl_cmd_parse2() and send those back to the CTRL command sender as reply. Retain the previous "Command parser error" reply only in case ctrl_cmd_parse2() should return NULL, which shouldn't actually happen at all. Change-Id: Ie35a02555b76913bb12734a76fc40fde7ffb244d http://cgit.osmocom.org/libosmocore/commit/?id=29ed24daee0351f5bd1947a74d0a… commit 29ed24daee0351f5bd1947a74d0a7c40fdf96d7f Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 01:05:25 2017 +0100 add ctrl_cmd_parse2() to return parsing errors If a control command fails to parse, we so far discard specific error messages and instead send just "Command parser error". In ctrl_cmd_parse() we actually compose detailed error replies, but in the end simply talloc_free() them and return NULL. A first step to report these errors to the ctrl command issuer is to not return NULL and instead return the cmd with type = CTRL_TYPE_ERROR. Add ctrl_cmd_parse2() to return such instead of NULL. To stay API compatible, provide ctrl_cmd_parse2() to return a cmd on errors. ctrl_cmd_parse() retains identical behavior but becomes just a simple wrapper around ctrl_cmd_parse2() which discards the cmd on error. No need really to deprecate ctrl_cmd_parse() yet; especially as long as compiler warnings might break jenkins builds. Change-Id: I5047c9f977d70b03eea77cbcfd2b96d43ea46880 http://cgit.osmocom.org/libosmocore/commit/?id=41eec760c14a594042daab768e85… commit 41eec760c14a594042daab768e85e4a04d20dfc4 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Fri Dec 15 20:41:28 2017 +0100 ctrl_test: add two more current parsing bugs to prep for fix Change-Id: Id11bc326be2f0bc2746a928354e416495a18baf7 http://cgit.osmocom.org/libosmocore/commit/?id=6115231b49382c6b21677c8ec985… commit 6115231b49382c6b21677c8ec985f61af93383c3 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 04:05:21 2017 +0100 ctrl: fix mem leak when handling GET_REPLY and SET_REPLY In ctrl_handle_msg() (code recently propagated from handle_control_read()), talloc_free() the parsed ctrl_cmd in all code paths. In particular, a free was missing in case ctrl_cmd_handle() returns CTRL_CMD_HANDLED. CTRL_CMD_HANDLED is triggered by GET_REPLY / SET_REPLY parsing, as show by ctrl_test.c. With the memleak fixed, adjust expected test output and make a detected mem leak abort the test immediately. Change-Id: Id583b413f8b8bd16e5cf92a8a9e8663903646381 http://cgit.osmocom.org/libosmocore/commit/?id=3ddb493599b61fcbe7dddb29ab6e… commit 3ddb493599b61fcbe7dddb29ab6ed3a13914648c Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 04:01:54 2017 +0100 ctrl_test: show memleak when receiving GET_REPLY and SET_REPLY commands The "memleak!" output shows messages that lack a talloc_free() of the parsed ctrl command buffer. The leak shall be fixed in a subsequent patch. Change-Id: I2c3e4d08b769b9cd77593362ea36a28d681cd042 http://cgit.osmocom.org/libosmocore/commit/?id=86f9b1902cb0294a2b3c096dce88… commit 86f9b1902cb0294a2b3c096dce88a15439d1d661 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 05:38:37 2017 +0100 ctrl_test: expand to test message handling and detect mem leaks Subsequent patches that tighten CTRL input validation will make the results more interesting. Change-Id: Idd4cc7d193db1a7d761f72ed33ed46eea450a78f http://cgit.osmocom.org/libosmocore/commit/?id=32c8f8ac9999a0fa0791a7ef1bdd… commit 32c8f8ac9999a0fa0791a7ef1bdd87210876e15f Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 03:57:56 2017 +0100 ctrl: prep test: separate new ctrl_handle_msg() from handle_control_read() In order to allow unit testing the ctrl iface msgb handling, have a separate msgb entry point function from the actual fd read function. An upcoming patch will prove a memory leak in CTRL msgb handling by a unit test that needs this separation. Change-Id: Ie09e39db668b866eeb80399b82e7b04b8f5ad7c3 http://cgit.osmocom.org/libosmocore/commit/?id=d8ad45804a605d9c0f22725aecf9… commit d8ad45804a605d9c0f22725aecf9a38450a35e31 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 01:03:37 2017 +0100 ctrl_test.c: replace print_escaped() with new osmo_escape_str() Change-Id: I12d3828dcc925f97fde11c360f1d60f3bd8cad8b http://cgit.osmocom.org/libosmocore/commit/?id=5674c182b620bd7cb2c5a175382f… commit 5674c182b620bd7cb2c5a175382f8e72cecea1cf Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 00:54:52 2017 +0100 utils: add osmo_escape_str() To report invalid characters in identifiers, it is desirable to escape any weird characters. Otherwise we might print stray newlines or control characters in the log output. ctrl_test.c already uses a print_escaped() function, which will be replaced by osmo_escape_str() in a subsequent patch. control_cmd.c will use osmo_escape_str() to log invalid identifiers. Change-Id: Ic685eb63dead3967d01aaa4f1e9899e5461ca49a ----------------------------------------------------------------------- Summary of changes: include/osmocom/crypt/auth.h | 2 ++ src/gsm/auth_core.c | 13 +++++++++++++ src/gsm/gsm0808.c | 3 ++- src/gsm/libosmogsm.map | 1 + src/gsm/milenage/milenage.c | 3 +-- src/rate_ctr.c | 3 +++ src/utils.c | 6 +++--- tests/ctrl/ctrl_test.c | 1 - tests/gsm0808/gsm0808_test.c | 2 +- tests/stats/stats_test.c | 7 ++++++- 10 files changed, 32 insertions(+), 9 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

7 years, 6 months

osmocom-bb.git branch fixeria/trx_tch deleted. osmocon_v0.0.0-1952-g097d19a0

by gitosis＠osmocom.org

This 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 "The Open Source GSM Base Band stack". The branch, fixeria/trx_tch has been deleted was 097d19a062ffffebed98430d9170e4087efde84b ----------------------------------------------------------------------- 097d19a062ffffebed98430d9170e4087efde84b host/trxcon/l1ctl.c: handle L1CTL_TRAFFIC_REQ ----------------------------------------------------------------------- hooks/post-receive -- The Open Source GSM Base Band stack

7 years, 6 months

osmocom-bb.git branch fixeria/trx updated. osmocon_v0.0.0-1993-gfeec102a

by gitosis＠osmocom.org

This 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 "The Open Source GSM Base Band stack". The branch, fixeria/trx has been updated via feec102aea039c4091fa9cf6075d45fd23448bd3 (commit) via 44838f79a2408feca664980d4b42a5c86b17db07 (commit) via 255f25ef25c5ce1deefcfbe63844bc47d524c377 (commit) via 32c2a1d74c1bb3f1cfa9a56b2e15b93fa321f942 (commit) via a403215beab8f92f7bd90fe8f80535bd61841b30 (commit) via 15d512d301545e10f69ade0562d5ea86832066b4 (commit) via e17bb11c3b29919799b3637dece1c7c0273af304 (commit) from 60ff614446fedc7b12767d9520abfc529a65fc7e (commit) 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/osmocom-bb/commit/?id=feec102aea039c4091fa9cf6075d4… commit feec102aea039c4091fa9cf6075d45fd23448bd3 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Mon Dec 18 05:47:28 2017 +0700 trxcon/scheduler: implement A5/X ciphering support This change implements the A5/X ciphering support transparently for the logical channel handlers. In other words, a DL burst is deciphered before being passed to a handler, and an UL burst is ciphered before being sent to transceiver. The implementation mostly relays on the libosmocore's A5 API. Change-Id: Ib53418d8c0f394fdece09cf5cc240887cb0bb5af http://cgit.osmocom.org/osmocom-bb/commit/?id=44838f79a2408feca664980d4b42a… commit 44838f79a2408feca664980d4b42a5c86b17db07 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Mon Dec 18 05:45:27 2017 +0700 trxcon/scheduler: preprocess UL bursts before sending Having a possibility to preprocess UL burst before sending to transceiver is required for the further ciphering support integration and probably some other tasks. Change-Id: Ia6eead5d4f51d7c0bf277b9d5ebb0a74676df567 http://cgit.osmocom.org/osmocom-bb/commit/?id=255f25ef25c5ce1deefcfbe63844b… commit 255f25ef25c5ce1deefcfbe63844bc47d524c377 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Sat Dec 16 17:52:31 2017 +0700 L1CTL/L1CTL_CRYPTO_REQ: add key length and channel info Previously, the L1CTL_CRYPTO_REQ message contained only a ciphering algorithm and actual Kc key to be used. The key length was calculated manually using the MSGB API. Let's avoid manual calculations here, as it may cause unexpected behavior if the message structure is changed. Also, let's fill the UL header with minimal information about a channel, which is going to be encrypted. Change-Id: I1813a188e755141241273479b17896415abcc3f1 http://cgit.osmocom.org/osmocom-bb/commit/?id=32c2a1d74c1bb3f1cfa9a56b2e15b… commit 32c2a1d74c1bb3f1cfa9a56b2e15b93fa321f942 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Mon Dec 18 04:39:27 2017 +0700 trxcon/scheduler: prioritize FACCH correctly Previously we used to compare two consecutive first primitives, taken from a transmit queue. This approach may cause some delay, which is critical for FACCH e.g. in case of handover. Let's walk through a whole transmit queue to find a pair of both FACCH frames, and only then decide what to do. Change-Id: I925cca77bfaa255dd095bc882c901d41c9bc4633 http://cgit.osmocom.org/osmocom-bb/commit/?id=a403215beab8f92f7bd90fe8f8053… commit a403215beab8f92f7bd90fe8f80535bd61841b30 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Mon Dec 18 03:47:23 2017 +0700 trxcon/scheduler: move prim management outside lchan handlers Previously, each lchan handler used to obtain and delete primitives from a timeslot's tranmit queue itself. This approach entails many potential problems and bugs: - The lchan handlers shall not do that by definition, they should encode and decode frames according to GSM 05.03. - In some cases (e.g. TCH), a single transmit queue may contain primitives of different types (e.g. TCH, FACCH and SACCH). At the same time, the lchan handlers don't care and don't even know about each other. So, this could cause an unexpected behaviour in some cases. This change separates all primitive management routines, providing a new API for obtaining and dropping them. "Write programs that do one thing and do it well." Change-Id: I29503ece51903784bc53541015285234471c8d15 http://cgit.osmocom.org/osmocom-bb/commit/?id=15d512d301545e10f69ade0562d5e… commit 15d512d301545e10f69ade0562d5ea86832066b4 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Mon Dec 18 02:13:41 2017 +0700 trxcon/scheduler: separate primitive management code It's good to write, keep and make the source code as much modular as possible. So, Tte primitive management code was separated to the 'sched_prim.c' and going to be extended in the near future. Change-Id: Ifec8c9e4f2c95c72b00772688bcb5dc9c11d6de7 http://cgit.osmocom.org/osmocom-bb/commit/?id=e17bb11c3b29919799b3637dece1c… commit e17bb11c3b29919799b3637dece1c7c0273af304 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Mon Dec 18 01:23:03 2017 +0700 trxcon/scheduler: BUGFIX: distinguish between SACCH and FACCH Both SACCH and FACCH messages have the same 23-byte length, both are being queued together within a single transimt queue. So, previously a SACCH frame could be picked by TCH burst handler, and then sent as a FACCH frame. Let's fix this. A FACCH primitive may have one of the TRXC_TCH* logical channel types, while SACCH primitives have one of the TRXC_SACCH*. Change-Id: Ia7090384f3ff74c9d94997265135acbceffa0ffe ----------------------------------------------------------------------- Summary of changes: include/l1ctl_proto.h | 1 + src/host/layer23/include/osmocom/bb/common/l1ctl.h | 4 +- src/host/layer23/src/common/l1ctl.c | 8 +- src/host/layer23/src/mobile/gsm48_rr.c | 12 +- src/host/trxcon/Makefile.am | 1 + src/host/trxcon/l1ctl.c | 58 ++++- src/host/trxcon/sched_lchan_common.c | 46 ---- src/host/trxcon/sched_lchan_rach.c | 25 +- src/host/trxcon/sched_lchan_sch.c | 1 - src/host/trxcon/sched_lchan_tchf.c | 58 ++--- src/host/trxcon/sched_lchan_xcch.c | 38 +--- src/host/trxcon/sched_prim.c | 251 +++++++++++++++++++++ src/host/trxcon/sched_trx.c | 206 +++++++++-------- src/host/trxcon/sched_trx.h | 18 +- src/target/firmware/layer1/l23_api.c | 5 +- 15 files changed, 500 insertions(+), 232 deletions(-) create mode 100644 src/host/trxcon/sched_prim.c hooks/post-receive -- The Open Source GSM Base Band stack

7 years, 6 months

libosmocore.git branch master updated. 0.10.2-60-g937ddea6

by gitosis＠osmocom.org

This 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 "An utility library for Open Source Mobile Communications". The branch, master has been updated via 937ddea6cce45f3f6dcb8177ea86162f15ecb5f9 (commit) via e5a2bdbc5501b892605a6a1fe7e30fb2f1546d42 (commit) from 3ef14a241afc123560e9a50d17948b040481b299 (commit) 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/libosmocore/commit/?id=937ddea6cce45f3f6dcb8177ea86… commit 937ddea6cce45f3f6dcb8177ea86162f15ecb5f9 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 00:46:50 2017 +0100 utils: add osmo_separated_identifiers_valid() For validating CTRL input, we want to verify that an input variable is a series of valid osmo_identifier_valid() separated by dots. Allow validating any additional chars with identifiers, for CTRL vars will be just ".". Change-Id: I13dfd02c8c870620f937d789873ad84c6b1c45de http://cgit.osmocom.org/libosmocore/commit/?id=e5a2bdbc5501b892605a6a1fe7e3… commit e5a2bdbc5501b892605a6a1fe7e30fb2f1546d42 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Sat Dec 16 04:54:37 2017 +0100 fix osmo_identifier_valid(): only allow printable characters In particular disallow ASCII 0..31 (control characters) and 127 (DEL). Change-Id: I04469988495af03c881fe81d7786ca7f71636299 ----------------------------------------------------------------------- Summary of changes: include/osmocom/core/utils.h | 1 + src/utils.c | 23 +++++++++++++++++++---- 2 files changed, 20 insertions(+), 4 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

7 years, 6 months

libosmocore.git branch master updated. 0.10.2-58-g3ef14a24

by gitosis＠osmocom.org

This 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 "An utility library for Open Source Mobile Communications". The branch, master has been updated via 3ef14a241afc123560e9a50d17948b040481b299 (commit) from 62e40855c2b1b50627dba5b187be8869e2cb2054 (commit) 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/libosmocore/commit/?id=3ef14a241afc123560e9a50d1794… commit 3ef14a241afc123560e9a50d17948b040481b299 Author: Max <msuraev(a)sysmocom.de> Date: Fri Dec 15 20:19:10 2017 +0100 Do not allocate already existing counter group Check that no group with the given name and index already exist before allocating it. Add corresponding test case. Change-Id: I563764af1d28043e909234ebb048239125ce6ecd Related: OS#2757 ----------------------------------------------------------------------- Summary of changes: src/rate_ctr.c | 3 +++ tests/stats/stats_test.c | 7 ++++++- 2 files changed, 9 insertions(+), 1 deletion(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

7 years, 6 months

libosmocore.git branch master updated. 0.10.2-57-g62e40855

by gitosis＠osmocom.org

This 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 "An utility library for Open Source Mobile Communications". The branch, master has been updated via 62e40855c2b1b50627dba5b187be8869e2cb2054 (commit) from 84ea2e037490a9ad6c0a192cf237f88fd83cdd88 (commit) 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/libosmocore/commit/?id=62e40855c2b1b50627dba5b187be… commit 62e40855c2b1b50627dba5b187be8869e2cb2054 Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Dec 17 20:50:34 2017 +0100 gsm0808_create_cipher_reject: Fix encoding of Cause IE The Cause IE in the 08.08 CIPHER MODE REJECT is a normal TLV IE, and not just a value. Let's make sure we encode the cause value properly. Change-Id: I4f5b231edf6dcb0a9c2bbafb2a59f301f3b2402b Closes: OS#2766 ----------------------------------------------------------------------- Summary of changes: src/gsm/gsm0808.c | 3 ++- tests/gsm0808/gsm0808_test.c | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

7 years, 6 months

osmo-bts.git branch laforge/omldummy created. 0.7.0-33-ge990d6d

by gitosis＠osmocom.org

This 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 "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, laforge/omldummy has been created at e990d6d49a694f2dfad5135088e5de871217f0af (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-bts/commit/?id=e990d6d49a694f2dfad5135088e5de8… commit e990d6d49a694f2dfad5135088e5de871217f0af Author: Harald Welte <laforge(a)gnumonks.org> Date: Sun Dec 17 13:35:52 2017 +0100 HACK: Add 'osmo-bts-omldummy' to bring up only OML without RSL This is used only in integration testing, where in the TTCN-3 testsuite we currently have no A-bis OML implementation, but only a RSL one. Change-Id: Id8e5f34091e6e32621d8c8673de7ea848dfd252f ----------------------------------------------------------------------- hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

7 years, 6 months

osmo-hlr.git branch master updated. 0.1.0-21-gb5d7701

by gitosis＠osmocom.org

This 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, master has been updated via b5d77012d1d74bbb28b07a374c436045ed3e43ea (commit) via fc96f688d4cfe339a6e5db14e4345270ce16ce11 (commit) from 43bd6069e83ff034dcaff4780891d0468e899b07 (commit) 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-hlr/commit/?id=b5d77012d1d74bbb28b07a374c43604… commit b5d77012d1d74bbb28b07a374c436045ed3e43ea Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Fri Dec 15 19:06:59 2017 +0100 contrib:jenkins.sh: Enable Werror Change-Id: I61688a4c9b50f6f3705bd18c96c00f8703ef5042 http://cgit.osmocom.org/osmo-hlr/commit/?id=fc96f688d4cfe339a6e5db14e434527… commit fc96f688d4cfe339a6e5db14e4345270ce16ce11 Author: Pau Espin Pedrol <pespin(a)sysmocom.de> Date: Fri Dec 15 19:05:08 2017 +0100 luop.c: Transform FIXME from warning to pragma message This way the issue is still visible but we can enable Werror to avoid introducing new warnings. Change-Id: I6c9b195bf0e3f853e202cdbdb72d35d83cd2a2ab ----------------------------------------------------------------------- Summary of changes: contrib/jenkins.sh | 2 +- src/luop.c | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) hooks/post-receive -- UNNAMED PROJECT

7 years, 6 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog