From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] b20d70: device: fix loss BREDR info when merge duplicate d...
Date: Sat, 10 Oct 2026 02:07:39 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1182833/000000-b20d70@github.com> (raw)
Branch: refs/heads/1182833
Home: https://github.com/bluez/bluez
Commit: b20d70c19997479424bf8d65810d440cc75dd270
https://github.com/bluez/bluez/commit/b20d70c19997479424bf8d65810d440cc75dd270
Author: Ye He <ye.he@amlogic.com>
Date: 2026-10-10 (Sat, 10 Oct 2026)
Changed paths:
M src/device.c
Log Message:
-----------
device: fix loss BREDR info when merge duplicate device
Two device objects for the same device in case it has
first been discovered over BREDR and has a private
address when discovered over LE for the next time.
The merge logic doesn't create a new BREDR bearer.
Makes the application loss connection info of BREDR.
Signed-off-by: Ye He <ye.he@amlogic.com>
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-10 9:07 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/1182833/000000-b20d70@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