osmocom-bb.git branch laforge/trx updated. osmocon_v0.0.0-2042-ge014ee1e

gitosis at osmocom.org gitosis at osmocom.org
Thu Mar 1 13:43:15 UTC 2018


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, laforge/trx has been updated
  discards  f287729db386580604e1535266897ac214cbd0ed (commit)
  discards  491327fd2589da78cf54fa0edf3c9137ef9bf8b2 (commit)
  discards  c963f1ff6c6e2cd6cde44783f56d8f292d1f259c (commit)
  discards  d4078e183053066625d75c59b8b7f672f6b628d3 (commit)
       via  e014ee1ed3bcd2c4ecd5d55259029ff3f78046b4 (commit)
       via  0d3030c76405fbcf3d8cbcb61547eee53aec02b3 (commit)
       via  380dc7e768c944ab0efc28f24205334a4c736a42 (commit)
       via  cc447afe3475a60c4745206ee219e20aa60494bd (commit)
       via  4e74311b00363b2ba417d7ca3ed67abfab1eaec8 (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 (f287729db386580604e1535266897ac214cbd0ed)
            \
             N -- N -- N (e014ee1ed3bcd2c4ecd5d55259029ff3f78046b4)

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/osmocom-bb/commit/?id=e014ee1ed3bcd2c4ecd5d55259029ff3f78046b4

commit e014ee1ed3bcd2c4ecd5d55259029ff3f78046b4
Author: Harald Welte <laforge at gnumonks.org>
Date:   Wed Feb 28 22:52:47 2018 +0100

    fake_trx: Log IP/Port information at start-up
    
    Change-Id: I4ebeed7271d91ab2e45199e0fb59776c00ad833c

http://cgit.osmocom.org/osmocom-bb/commit/?id=0d3030c76405fbcf3d8cbcb61547eee53aec02b3

commit 0d3030c76405fbcf3d8cbcb61547eee53aec02b3
Author: Harald Welte <laforge at gnumonks.org>
Date:   Thu Mar 1 14:40:32 2018 +0100

    trxcon: Fix '-i' to specify the "TRX IP address"
    
    The command line help states '-i' is for 'TRX IP address', which is
    the remote IP address at which the TRX is to be found.  Hoewever, it
    was used as the local (bind) IP address of the socket used towards
    the TRX.  This is my attempt at fixing this.  A more complete solution
    probably allows to specify both local (bind) and remote (connect)
    address, just to be clear.
    
    Change-Id: If0252b15e9c7942687c6dc470951d777f7af651c

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

Summary of changes:
 src/host/trxcon/trx_if.c | 45 ++++++++++++---------------------------------
 src/host/trxcon/trx_if.h |  3 ++-
 src/host/trxcon/trxcon.c |  2 +-
 3 files changed, 15 insertions(+), 35 deletions(-)


hooks/post-receive
-- 
The Open Source GSM Base Band stack


More information about the osmocom-commitlog mailing list