From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221524] Intel 8265 Bluetooth regression (BLE hearing aid unusable) in kernel 6.12 vs 6.1
Date: Fri, 15 May 2026 12:14:05 +0000 [thread overview]
Message-ID: <bug-221524-62941-C9l466Q6Ia@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221524-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221524
Darek (t.darcin10@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Intel 8265 Bluetooth |Intel 8265 Bluetooth
|(8087:0a2b) BLE |regression (BLE hearing aid
|connectivity regression |unusable) in kernel 6.12 vs
|observed after kernel |6.1
|upgrade. |
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2026-05-15 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 12:12 [Bug 221524] New: Intel 8265 Bluetooth (8087:0a2b) BLE connectivity regression observed after kernel upgrade bugzilla-daemon
2026-05-15 12:14 ` bugzilla-daemon [this message]
2026-05-15 13:26 ` [Bug 221524] Intel 8265 Bluetooth regression (BLE hearing aid unusable) in kernel 6.12 vs 6.1 bugzilla-daemon
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=bug-221524-62941-C9l466Q6Ia@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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