From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 5d183b: monitor: Add Minimum Supported Connection Interval
Date: Tue, 13 Oct 2026 11:32:35 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1184798/000000-9db197@github.com> (raw)
Branch: refs/heads/1184798
Home: https://github.com/bluez/bluez
Commit: 5d183b9b980e191e8a14bc37bdd1ad60db6e2611
https://github.com/bluez/bluez/commit/5d183b9b980e191e8a14bc37bdd1ad60db6e2611
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-10-13 (Tue, 13 Oct 2026)
Changed paths:
M monitor/bt.h
M monitor/packet.c
Log Message:
-----------
monitor: Add Minimum Supported Connection Interval
The LE Read Connection Interval response carries a
Minimum_Supported_Connection_Interval octet between the status and
Num_Groups, in units of 125 us with a range of 0x03 to 0x3C. Add it to
the structure and decode it.
Assisted-by: OpenCode:claude-opus-5.5
Commit: 9db1974ad9b910f12a29dc3ef75f26ccd1df5779
https://github.com/bluez/bluez/commit/9db1974ad9b910f12a29dc3ef75f26ccd1df5779
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-10-13 (Tue, 13 Oct 2026)
Changed paths:
M emulator/btdev.c
Log Message:
-----------
emulator: Add Minimum Supported Connection Interval
Fill the Minimum_Supported_Connection_Interval octet of the LE Read
Connection Interval response, reporting 1 ms, the same lower bound as
the interval group already returned.
Assisted-by: OpenCode:claude-opus-5.5
Compare: https://github.com/bluez/bluez/compare/5d183b9b980e%5E...9db1974ad9b9
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-13 18:32 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/1184798/000000-9db197@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