From: mdzik-sue <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b6b0a7: adapter: remove bondable mode hijacking when setti...
Date: Tue, 22 Sep 2026 04:45:47 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1171262/000000-b6b0a7@github.com> (raw)
Branch: refs/heads/1171262
Home: https://github.com/bluez/bluez
Commit: b6b0a74998f14f16f62c2924cdb874d7f640b4e0
https://github.com/bluez/bluez/commit/b6b0a74998f14f16f62c2924cdb874d7f640b4e0
Author: Michal Dzik <michal.dzik@streamunlimited.com>
Date: 2026-09-22 (Tue, 22 Sep 2026)
Changed paths:
M src/adapter.c
Log Message:
-----------
adapter: remove bondable mode hijacking when setting IO capabilities
Setting IO capabilities could implicitly toggle bondable mode on or off.
This behavior was introduced by "core: Add AlwaysPairable to main.conf"
and creates unwanted side effects for external pairing handling,
specifically glitches in the Pairable property during BlueZ startup.
The unnecessary setting of MGMT_OP_SET_BONDABLE has no basis in the
Bluetooth specification and should be removed.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-22 11:45 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/1171262/000000-b6b0a7@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