From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b57f45: doc/org.bluez.ChannelSounding1:Add Used by referen...
Date: Tue, 14 Jul 2026 02:19:50 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1127251/000000-76701e@github.com> (raw)
Branch: refs/heads/1127251
Home: https://github.com/bluez/bluez
Commit: b57f4583cfe4a1eb34d886970339b6c7854c7b6c
https://github.com/bluez/bluez/commit/b57f4583cfe4a1eb34d886970339b6c7854c7b6c
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-14 (Tue, 14 Jul 2026)
Changed paths:
A doc/org.bluez.ChannelSounding1.rst
Log Message:
-----------
doc/org.bluez.ChannelSounding1:Add Used by reference and Examples
Add :Used by: field linking to bluetoothctl cs submenu and
Examples section showing corresponding bluetoothctl cs commands
for D-Bus methods
Commit: e1841462a7654678c76ad578e955710f69591d37
https://github.com/bluez/bluez/commit/e1841462a7654678c76ad578e955710f69591d37
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-14 (Tue, 14 Jul 2026)
Changed paths:
M Makefile.am
A doc/org.bluez.ChannelSoundingRanging1.rst
Log Message:
-----------
doc/org.bluez.ChannelSoundingRanging1:Add references and examples
Add :Used by: field linking to bluetoothctl cs submenu and
Examples section showing the corresponding bluetoothctl output
for the RangeEstimate signal
Commit: 0ceb0039ac98685986e02320670bf1c4af3da269
https://github.com/bluez/bluez/commit/0ceb0039ac98685986e02320670bf1c4af3da269
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-14 (Tue, 14 Jul 2026)
Changed paths:
M Makefile.tools
A doc/bluetoothctl-cs.rst
Log Message:
-----------
doc/bluetoothctl-cs: Add :Uses: fields and document arguments
Add :Uses: fields to link commands to their corresponding D-Bus API
methods, and document command arguments with usage examples.
Commit: 76701e5ddfd61d9948ef75f41213bbbc4ba8db13
https://github.com/bluez/bluez/commit/76701e5ddfd61d9948ef75f41213bbbc4ba8db13
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-07-14 (Tue, 14 Jul 2026)
Changed paths:
A client/scripts/cs-initiator.bt
A client/scripts/cs-reflector.bt
Log Message:
-----------
client: Add scripts to start cs Initiator/reflector
This adds sample bluetoothctl scripts for cs initiator/
reflector.
cs-initiator.bt sets up and runs a CS measurement as an Initiator
cs-reflector.bt sets up the device to respond as a Reflector
Compare: https://github.com/bluez/bluez/compare/b57f4583cfe4%5E...76701e5ddfd6
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-14 9:19 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/1127251/000000-76701e@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