From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221339] AX200 -19 errors on boot after firmware 20260313-1.1
Date: Tue, 14 Apr 2026 07:04:43 +0000 [thread overview]
Message-ID: <bug-221339-62941-FLnc6SgBA5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221339-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221339
The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |regressions@leemhuis.info
--- Comment #5 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
(In reply to pallaswept from comment #4)
> keep it in mind for next time.
It's even more complicated, as this bugzilla for most of the kernel is the
wrong place to report bugs (long story), as most reports here do not even reach
the right developers.
> Yes I have confirmed that it was that file, if I roll back to the previous
> version the issues are resolved.
Can I forward this report by mail? This would expose your email address to the
public
--
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-04-14 7:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 16:53 [Bug 221339] New: AX200 -19 errors on boot after firmware 20260313-1.1 bugzilla-daemon
2026-04-10 7:36 ` [Bug 221339] " bugzilla-daemon
2026-04-10 9:16 ` bugzilla-daemon
2026-04-10 9:18 ` bugzilla-daemon
2026-04-10 9:21 ` bugzilla-daemon
2026-04-14 7:04 ` bugzilla-daemon [this message]
2026-04-14 7:16 ` bugzilla-daemon
2026-04-14 7:27 ` bugzilla-daemon
2026-04-18 4:34 ` bugzilla-daemon
2026-04-20 11:36 ` bugzilla-daemon
2026-04-20 11:37 ` bugzilla-daemon
2026-04-20 11:56 ` bugzilla-daemon
2026-04-21 5:07 ` 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-221339-62941-FLnc6SgBA5@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