From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 93792c: src: Modify MaxTxPower option documentation for Ch...
Date: Thu, 20 Aug 2026 11:16:03 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1149256/000000-b625e4@github.com> (raw)
Branch: refs/heads/1149256
Home: https://github.com/bluez/bluez
Commit: 93792cbd6e832cea4f958a07d3841444d2381311
https://github.com/bluez/bluez/commit/93792cbd6e832cea4f958a07d3841444d2381311
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-20 (Thu, 20 Aug 2026)
Changed paths:
M src/main.conf
Log Message:
-----------
src: Modify MaxTxPower option documentation for ChannelSounding
Modify MaxTxPower configuration option to take decimal values
within the range of -127dBm to 20dBm
Defaults to 20 (max power).
Commit: b625e4eb5057868b972a305aa0b2eaf5c27de0ff
https://github.com/bluez/bluez/commit/b625e4eb5057868b972a305aa0b2eaf5c27de0ff
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-20 (Thu, 20 Aug 2026)
Changed paths:
M client/cs.c
Log Message:
-----------
client: Enforce Valid Main Mode and Sub Mode Combinations
Introduce validation for main_mode_type and sub_mode_type combinations as
specified in the protocol requirements.
Reject invalid combinations and guide the user by displaying
the acceptable mode pairings.
Compare: https://github.com/bluez/bluez/compare/93792cbd6e83%5E...b625e4eb5057
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-20 18: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/1149256/000000-b625e4@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