From: cochcoder <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 02aa5e: monitor: Add Minimum Supported Connection Interval
Date: Wed, 14 Oct 2026 10:32:20 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/9dc7e4-dd9d5b@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 02aa5ea219edb9d4c4bae700fd978de8da5d787a
https://github.com/bluez/bluez/commit/02aa5ea219edb9d4c4bae700fd978de8da5d787a
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: 8ebf7ffe7bc6ceb15d908073673f251ca3939df0
https://github.com/bluez/bluez/commit/8ebf7ffe7bc6ceb15d908073673f251ca3939df0
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
Commit: 0a48b5ef5e3d55e3ce0cf1a462ff49c3f465f329
https://github.com/bluez/bluez/commit/0a48b5ef5e3d55e3ce0cf1a462ff49c3f465f329
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-10-13 (Tue, 13 Oct 2026)
Changed paths:
M test/functional/test_bap.py
Log Message:
-----------
test: functional: connect instead of pairing a bonded BAP device
The hosts are shared between tests, so a device bonded by an earlier one
is still bonded when a later one pairs it, and pairing it again fails
with AlreadyExists. cmd_pair is meant to connect it instead, but it
checks Paired, which is not set until the services are resolved, so it
can still issue the pairing:
FAILED test/functional/test_bap.py::test_bass_past_transport_acquire
AssertionError: Failed to pair: org.bluez.Error.AlreadyExists
Check Bonded, which is what the pairing is rejected for, and connect the
device instead when it is set.
Assisted-by: OpenCode:claude-opus-5.5
Commit: dd9d5ba1fa4f682b082b1275a8c38523d95a58fd
https://github.com/bluez/bluez/commit/dd9d5ba1fa4f682b082b1275a8c38523d95a58fd
Author: Kyle Pepper <cochcoder@proton.me>
Date: 2026-10-14 (Wed, 14 Oct 2026)
Changed paths:
M tools/mgmt-tester.c
Log Message:
-----------
mgmt-tester: Add host-resolved RPA scan checks
Check unfiltered passive scanning for IRK peers on controllers without
LL Privacy, with auto-connect and background-report controls.
Assisted-by: OpenCode:gpt-6.1-sol
Compare: https://github.com/bluez/bluez/compare/9dc7e40962f1...dd9d5ba1fa4f
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-14 17: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/master/9dc7e4-dd9d5b@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