From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 218264] Potential kernel regression with bluetooth pairing on specific radios
Date: Thu, 21 Dec 2023 14:12:59 +0000 [thread overview]
Message-ID: <bug-218264-62941-x7wDDMcxWB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218264-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218264
--- Comment #6 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
(In reply to Marco from comment #5)
> Bluetooth regression AND hid regression or this can be caused only by
> bluetooth driver shenanigans?
Hard to tell. But I fear that no developer will look into this unless you
perform a bisection. But before you do so you likely want to test mainline and
a working kernel on the same installation (e.g. not with live linux or anything
where more than the kernel changed)
Side note, FWIW: I have no idea if the bluetooth devs are even listening here.
To udnerstand why, search for "bugzilla" in
https://docs.kernel.org/admin-guide/reporting-issues.html and
https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/
--
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:[~2023-12-21 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 15:35 [Bug 218264] New: Potential kernel regression with bluetooth pairing on specific radios bugzilla-daemon
2023-12-17 7:32 ` [Bug 218264] " bugzilla-daemon
2023-12-17 14:54 ` bugzilla-daemon
2023-12-17 15:51 ` bugzilla-daemon
2023-12-17 18:32 ` bugzilla-daemon
2023-12-21 12:43 ` bugzilla-daemon
2023-12-21 14:12 ` bugzilla-daemon [this message]
2024-02-08 16:00 ` 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-218264-62941-x7wDDMcxWB@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;
as well as URLs for NNTP newsgroup(s).