From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 66d19b: bap: fixed the return value of GIOFunc
Date: Wed, 29 Jul 2026 09:40:26 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/729f96-98e5a7@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 66d19bb2a02792cf30cd723b65d4c2110930a31e
https://github.com/bluez/bluez/commit/66d19bb2a02792cf30cd723b65d4c2110930a31e
Author: Yang Li <yang.li@amlogic.com>
Date: 2026-07-29 (Wed, 29 Jul 2026)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: fixed the return value of GIOFunc
The GIOFunc should return FALSE if the event source should be removed.
Fixes: 322c39a64 ("bap: Start BIG sync after receiving BIGInfo")
Commit: fee4813d90af02c5f3882461ee6a1bc1d84931f2
https://github.com/bluez/bluez/commit/fee4813d90af02c5f3882461ee6a1bc1d84931f2
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-29 (Wed, 29 Jul 2026)
Changed paths:
M src/shared/rap.c
M src/shared/rap.h
Log Message:
-----------
rap: use session lookup for RAS operations
Store disconnect information in RAP state and
centralize attachment handling through dedicated helpers.
Add bt_rap_get_session() and use it from all RAS
GATT server callbacks
Commit: 98e5a74736e218f08b9928a931e4d537735fd2d8
https://github.com/bluez/bluez/commit/98e5a74736e218f08b9928a931e4d537735fd2d8
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-29 (Wed, 29 Jul 2026)
Changed paths:
M profiles/ranging/rap.c
Log Message:
-----------
profiles: centralize reflector setup
Add a helper for reflector initialization and track D-Bus registration
state in rap_data. Simplify connection handling, move interface cleanup
to object destruction, and streamline removal logic.
Compare: https://github.com/bluez/bluez/compare/729f96089cf6...98e5a74736e2
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-29 16:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bluez/bluez/push/refs/heads/master/729f96-98e5a7@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.