From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] fc03db: input: Fix checking LE bonding on HIDP
Date: Tue, 21 Apr 2026 13:34:58 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1084033/000000-fc03db@github.com> (raw)
Branch: refs/heads/1084033
Home: https://github.com/bluez/bluez
Commit: fc03db8ad548a5676fe5401ed94caa54ea860bb9
https://github.com/bluez/bluez/commit/fc03db8ad548a5676fe5401ed94caa54ea860bb9
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-21 (Tue, 21 Apr 2026)
Changed paths:
M profiles/input/device.c
Log Message:
-----------
input: Fix checking LE bonding on HIDP
HIDP is classic only, LE uses HOG, so there is no point in checking the
bonding with the address type which in case the device supports
dual-mode will map to LE random/public address.
Fixes: https://github.com/bluez/bluez/issues/2034
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-21 20:34 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/1084033/000000-fc03db@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