regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #forregzbot
Date: Thu, 5 May 2022 09:45:00 +0200	[thread overview]
Message-ID: <5da7d9bb-7c1a-63c1-e274-ae10cc465c3f@leemhuis.info> (raw)
In-Reply-To: <be67a3cf-44a2-7ea2-c0c3-29829b029e1b@leemhuis.info>



On 10.04.22 09:59, Thorsten Leemhuis wrote:
> On 09.04.22 13:00, Thorsten Leemhuis wrote:
>> TWIMC: this mail is primarily send for documentation purposes and for
>> regzbot, my Linux kernel regression tracking bot. These mails usually
>> contain '#forregzbot' in the subject, to make them easy to spot and filter.
>>
>> About a week ago a regression was reported to bugzilla.kernel.org that
>> seems to be handled there already, nevertheless I'd like to add to the
>> tracking to ensure it's not forgotten.
>>
>> #regzbot introduced: v5.16..v5.17
>> #regzbot from: Winston Wu <winstonwu91@gmail.com>
>> #regzbot title: net: bluetooth: Basilisk X Hyperspeed Bluetooth LE mouse
>> fail to connect under 5.17 with Opcode 0x2043 failure
>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215725
> 
> #regzbot monitor:
> https://lore.kernel.org/all/bug-215725-62941@https.bugzilla.kernel.org%2F/
> #regzbot ignore-activity

#regzbot invalid: doesn#t happen anymore with 5.17.3

      reply	other threads:[~2022-05-05  7:45 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 ` [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure Thorsten Leemhuis
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 [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=5da7d9bb-7c1a-63c1-e274-ae10cc465c3f@leemhuis.info \
    --to=regressions@leemhuis.info \
    --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).