From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 801a5c: shared: remove default settings params from bt_rap...
Date: Tue, 30 Jun 2026 04:35:10 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1118869/000000-9d4da6@github.com> (raw)
Branch: refs/heads/1118869
Home: https://github.com/bluez/bluez
Commit: 801a5c4d9c6fe13bf6e73e04a3b40c5a8fad7c8d
https://github.com/bluez/bluez/commit/801a5c4d9c6fe13bf6e73e04a3b40c5a8fad7c8d
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M src/shared/rap.h
Log Message:
-----------
shared: remove default settings params from bt_rap_attach_hci
role, cs_sync_ant_sel and max_tx_power were passed into bt_rap_attach_hci
but these are CS default settings that belong to the measurement session,
Callers need to set them via bt_rap_set_default_settings_params() in
start_measurement where they belong, alongside the other per-session
CS parameters
Commit: 66fd6c144600296a291bf54be58b9baa110d9e62
https://github.com/bluez/bluez/commit/66fd6c144600296a291bf54be58b9baa110d9e62
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M profiles/ranging/rap.c
M profiles/ranging/rap_hci.c
Log Message:
-----------
profiles: update bt_rap_attach_hci call to drop default settings args
role, cs_sync_ant_sel and max_tx_power are no longer passed at attach
time. They are applied via bt_rap_set_default_settings_params() in
start_measurement where they belong, alongside the other per-session
CS parameters
Commit: af7b71cf565f5fcfc3c8302b6adc6c6aa215586d
https://github.com/bluez/bluez/commit/af7b71cf565f5fcfc3c8302b6adc6c6aa215586d
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M src/btd.h
M src/main.c
M src/main.conf
Log Message:
-----------
rap: remove CS default settings from main.conf
role, cs_sync_ant_sel and max_tx_power were configurable in main.conf
and parsed in main.c, but these are per-measurement parameters that
callers supply via StartMeasurement
Commit: 15ba2adfd3d757bc88088854295242c3cea80e40
https://github.com/bluez/bluez/commit/15ba2adfd3d757bc88088854295242c3cea80e40
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M src/shared/rap.h
Log Message:
-----------
shared: replace the wrapper API
Replace API bt_rap_attach_hci_v2 with
bt_rap_attach_hci which has less parameters
to avoid compilation error for individual patches
Commit: 88e942cc79b1fe19ec5f0ecd8325f09fdf10424d
https://github.com/bluez/bluez/commit/88e942cc79b1fe19ec5f0ecd8325f09fdf10424d
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M profiles/ranging/rap.c
M profiles/ranging/rap_hci.c
Log Message:
-----------
profiles: replace wrapper API
replace bt_rap_attach_hci_v2 with bt_rap_attach_hci API
which has less parameters to avoid compilation error
in individual patchsets
Commit: 9d4da6e27b6cc928ca041f31e514b4952fb0613b
https://github.com/bluez/bluez/commit/9d4da6e27b6cc928ca041f31e514b4952fb0613b
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M src/shared/rap.h
Log Message:
-----------
shared: remove wrapper API
Remove bt_rap_attach_hci_v2 wrapper API
which was added to prevent compilation error
in individual patchsets
Compare: https://github.com/bluez/bluez/compare/801a5c4d9c6f%5E...9d4da6e27b6c
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-30 11:35 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/1118869/000000-9d4da6@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