From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] ede1b1: rap: use session lookup for RAS operations
Date: Tue, 21 Jul 2026 02:16:16 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1131452/000000-a12498@github.com> (raw)
Branch: refs/heads/1131452
Home: https://github.com/bluez/bluez
Commit: ede1b10d67642eba459a9b9b8860d844ded0997c
https://github.com/bluez/bluez/commit/ede1b10d67642eba459a9b9b8860d844ded0997c
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-21 (Tue, 21 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 instead of the previous accessed
notification bridge. As part of the cleanup,
remove the accessed callback registration APIs,
related notification code, and the unused timeout.h include
Commit: a12498ad4b814638833fd7a2f2b35e24ad4799b0
https://github.com/bluez/bluez/commit/a12498ad4b814638833fd7a2f2b35e24ad4799b0
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-21 (Tue, 21 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.
Remove the legacy RAS accessed callback path and its registration
handling from initialization and shutdown.
Compare: https://github.com/bluez/bluez/compare/ede1b10d6764%5E...a12498ad4b81
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-21 9:16 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/1131452/000000-a12498@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox