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 "Osmocom A-bis protcol interface library". The branch, master has been updated via 687046ba2f0527456ae47365a9709fc939fdaf48 (commit) from 37fcd93a508b52f6f33bf47191bba41cb7367b0d (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/libosmo-abis/commit/?id=687046ba2f0527456ae47365a9709fc939fdaf48 commit 687046ba2f0527456ae47365a9709fc939fdaf48 Author: Holger Hans Peter Freyther <holger at moiji-mobile.com> Date: Fri Dec 12 17:39:58 2014 +0100 ipa: Set the BSC_FD_WRITE in ipa_client_conn_open When the link is being created BSC_FD_WRITE and BSC_FD_READ are being ored into the flag. When the socket connects the first time the ipa_client_fd_cb function is called and the link->state is moved from connecting to connect. In case the connection drops and ipa_client_conn_open is called again the BSC_FD_WRITE flag might not be set. This means that after the socket is connected, ipa_client_fd_cb will not be called. This means that the updown_cb will not be called until after the first write or read on the socket. It might even lead to missing some data. When re-connecting set the write flag again. ----------------------------------------------------------------------- Summary of changes: src/input/ipa.c | 1 + 1 file changed, 1 insertion(+) hooks/post-receive -- Osmocom A-bis protcol interface library