From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
linux-bluetooth@vger.kernel.org, bugzilla-daemon@kernel.org
Subject: Re: [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure
Date: Tue, 29 Mar 2022 10:01:40 +0200 [thread overview]
Message-ID: <e2c9b59e-2b0f-8eab-def7-bc736b0ecce5@leemhuis.info> (raw)
In-Reply-To: <bug-215725-62941@https.bugzilla.kernel.org/>
Hi, this is your Linux kernel regression tracker.
On 22.03.22 14:38, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=215725
>
> Bug ID: 215725
> Summary: Basilisk X Hyperspeed Bluetooth LE mouse fail to
> connect under 5.17 with Opcode 0x2043 failure
Hey bluetooth maintainers, what's up here? That's a report about a
regression that was submitted more than a week ago. Has anything
happened to get it fixed? Reminder: this ideally should be fixed in
5.17.y before 5.16.y becomes EOL, which I guess will happen in round
about two or three weeks from now.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.
next parent reply other threads:[~2022-03-29 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215725-62941@https.bugzilla.kernel.org/>
2022-03-29 8:01 ` Thorsten Leemhuis [this message]
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-04-10 7:59 ` Thorsten Leemhuis
2022-05-05 7:45 ` Thorsten Leemhuis
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=e2c9b59e-2b0f-8eab-def7-bc736b0ecce5@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bugzilla-daemon@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=regressions@lists.linux.dev \
/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).