From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Regression] Logitech BT mouse unusable after commit 532223c8ac57 (still in 6.1-rc8) #forregzbot
Date: Fri, 9 Dec 2022 07:34:34 +0100 [thread overview]
Message-ID: <94dc3a77-738f-d801-9e5a-e3a61498e43b@leemhuis.info> (raw)
In-Reply-To: <abf9b7a0-8de4-76e9-bbbf-4630932949e9@leemhuis.info>
On 08.12.22 08:03, Thorsten Leemhuis wrote:
> [Note: this mail contains only information for Linux kernel regression
> tracking. Mails like these contain '#forregzbot' in the subject to make
> then easy to spot and filter out. The author also tried to remove most
> or all individuals from the list of recipients to spare them the hassle.]
>
> On 06.12.22 15:58, Rafael J. Wysocki wrote:
>>
>> Commit 532223c8ac57 ("HID: logitech-hidpp: Enable HID++ for all the Logitech
>> Bluetooth devices") caused my Logitech Bluetooth mouse to become unusable.
>> [...]
>
> Thanks for the report. To be sure below issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
> tracking bot:
>
> #regzbot ^introduced 532223c8ac57
> #regzbot title hid: Logitech BT mouse unusable
> #regzbot monitor:
> https://lore.kernel.org/all/20221207142433.1158329-1-benjamin.tissoires@redhat.com/
> #regzbot ignore-activity
#regzbot fix: a9d9e46c755a1
prev parent reply other threads:[~2022-12-09 6:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 14:58 [Regression] Logitech BT mouse unusable after commit 532223c8ac57 (still in 6.1-rc8) Rafael J. Wysocki
2022-12-07 8:58 ` Rafael J. Wysocki
2022-12-07 9:07 ` Bastien Nocera
2022-12-07 9:04 ` Bastien Nocera
2022-12-07 9:16 ` Rafael J. Wysocki
2022-12-07 9:36 ` Rafael J. Wysocki
2022-12-07 9:58 ` Bastien Nocera
2022-12-07 10:07 ` Rafael J. Wysocki
2022-12-07 10:50 ` Bastien Nocera
2022-12-07 11:07 ` Rafael J. Wysocki
2022-12-07 17:19 ` Bastien Nocera
2022-12-07 17:44 ` Rafael J. Wysocki
2022-12-08 15:20 ` Bastien Nocera
2022-12-13 16:14 ` Bastien Nocera
2022-12-15 15:09 ` Rafael J. Wysocki
2022-12-07 9:10 ` [PATCH v1 0/2] HID: Fix regression resulting from commit 532223c8ac57 Rafael J. Wysocki
2022-12-07 9:11 ` [PATCH v1 1/2] HID: generic: Add ->match() check to __check_hid_generic() Rafael J. Wysocki
2022-12-07 9:27 ` Benjamin Tissoires
2022-12-07 9:54 ` Rafael J. Wysocki
2022-12-07 9:12 ` [PATCH v1 2/2] HID: logitech-hidpp: Add Bluetooth Mouse M336/M337/M535 to unhandled_hidpp_devices[] Rafael J. Wysocki
2022-12-07 9:29 ` Bastien Nocera
2022-12-07 9:47 ` Rafael J. Wysocki
2022-12-07 9:59 ` Bastien Nocera
2022-12-07 10:05 ` Benjamin Tissoires
2022-12-07 10:11 ` Rafael J. Wysocki
2022-12-07 10:19 ` Jiri Kosina
2022-12-07 12:43 ` Bastien Nocera
2022-12-07 13:00 ` Rafael J. Wysocki
2022-12-07 13:24 ` Benjamin Tissoires
2022-12-07 13:39 ` Rafael J. Wysocki
2022-12-07 14:24 ` Bastien Nocera
2022-12-08 13:32 ` Benjamin Tissoires
2022-12-07 9:48 ` Benjamin Tissoires
2022-12-07 9:59 ` Bastien Nocera
2022-12-08 7:03 ` [Regression] Logitech BT mouse unusable after commit 532223c8ac57 (still in 6.1-rc8) #forregzbot Thorsten Leemhuis
2022-12-09 6:34 ` 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=94dc3a77-738f-d801-9e5a-e3a61498e43b@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).