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, master has been updated
       via  aa11997480822af0a583ac3c7c3fca1dc4bbe994 (commit)
       via  9a30b7781310b81555b216d32b172b6bb9c9d7e4 (commit)
      from  01e84be54f38c0458f3ee04111243ca0777baadc (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-bts/commit/?id=aa11997480822af0a583ac3c7c3fca1dc4bbe994

commit aa11997480822af0a583ac3c7c3fca1dc4bbe994
Author: Max <[email protected]>
Date:   Thu Aug 24 15:35:54 2017 +0200

    osmo-bts-trx: remove global variables from loops
    
    * move TA related globals into phy_link
    * move power loop related globals into phy_link
    * prefix corresponding vty vars with osmotrx
    
    Change-Id: I01d7c1abad67e51b886a4ecf2de072929d67da27
    Related: OS#1848

http://cgit.osmocom.org/osmo-bts/commit/?id=9a30b7781310b81555b216d32b172b6bb9c9d7e4

commit 9a30b7781310b81555b216d32b172b6bb9c9d7e4
Author: Max <[email protected]>
Date:   Thu Aug 24 15:54:48 2017 +0200

    osmo-bts-trx: fix 'osmotrx legacy-setbsic'
    
    It was introduced in fe6c75d24a1751341bcee91cb45c7ac7f5d07da3:
    
    * fix typo in config write
    * add missing vty help string
    
    Change-Id: Id42359dfbb8ad02f34dd2540db66f3ed69ad5181

-----------------------------------------------------------------------

Summary of changes:
 include/osmo-bts/phy_link.h |  4 ++-
 src/osmo-bts-trx/loops.c    | 18 ++++++-------
 src/osmo-bts-trx/loops.h    |  4 ---
 src/osmo-bts-trx/main.c     |  3 +++
 src/osmo-bts-trx/trx_vty.c  | 66 ++++++++++++++++++++++++---------------------
 5 files changed, 50 insertions(+), 45 deletions(-)


hooks/post-receive
-- 
Osmocom BTS-side code (Abis, scheduling, ...)

Reply via email to