From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221637] Regression for Intel Corporation Device a876 (rev 10)
Date: Mon, 15 Jun 2026 05:48:45 +0000 [thread overview]
Message-ID: <bug-221637-62941-LXCj5w3KNy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221637-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221637
--- Comment #8 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
Krian:
> the below patch.
FWIW a quick reminder, "[…] updated firmware files must not cause any
regressions for users of older kernel releases." -- that is a quote from
https://docs.kernel.org/driver-api/firmware/firmware-usage-guidelines.html
So fixing this with a kernel patch is nice, but by kernel standards this from
what I see still qualifies as a regression where the firmware change needs to
be reverted to avoid the problem.
That being said: if we assume that this is a corner case that only Bianca and
maybe one or two others hits, then using a patch is fine if it's fine for the
affected people. Is that the case?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2026-06-15 5:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 19:46 [Bug 221637] New: Regression for Intel Corporation Device a876 (rev 10) bugzilla-daemon
2026-06-10 20:03 ` [Bug 221637] " bugzilla-daemon
2026-06-11 14:29 ` bugzilla-daemon
2026-06-11 14:36 ` bugzilla-daemon
2026-06-11 14:41 ` bugzilla-daemon
2026-06-11 17:18 ` bugzilla-daemon
2026-06-12 6:57 ` bugzilla-daemon
2026-06-14 7:04 ` bugzilla-daemon
2026-06-14 23:41 ` bugzilla-daemon
2026-06-15 5:48 ` bugzilla-daemon [this message]
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-221637-62941-LXCj5w3KNy@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