From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215725] Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure
Date: Mon, 03 Oct 2022 10:54:44 +0000 [thread overview]
Message-ID: <bug-215725-62941-dSiUd4ETFs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215725-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215725
Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pmenzel+bugzilla.kernel.org
| |@molgen.mpg.de
--- Comment #5 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
(In reply to Winston Wu from comment #4)
> Hi it seems that the problem no longer presents after 5.17.3 or so…
Thank you for reporting back. If you have time, it’d be great if you could
figure out the exact commit. Otherwise, it’d be great if you closed the
issue/bug report.
PS: If you reply via email, please do not quote/cite the original email, as the
quote is not hidden in the Bugzilla comment, making it hard to read.
--
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:[~2022-10-03 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 13:38 [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure bugzilla-daemon
2022-03-29 8:01 ` Thorsten Leemhuis
2022-03-29 8:01 ` [Bug 215725] " bugzilla-daemon
2022-03-29 21:04 ` bugzilla-daemon
2022-04-09 11:00 ` [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #forregzbot Thorsten Leemhuis
2022-05-04 13:12 ` [Bug 215725] Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure bugzilla-daemon
2022-05-04 14:21 ` bugzilla-daemon
2022-10-03 10:54 ` 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-215725-62941-dSiUd4ETFs@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).