From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Bastien Nocera <hadess@hadess.net>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jikos@kernel.org>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] Bug 217353 - Logitech MX Anywhere 3 scroll wheel works incorrectly over USB dongle
Date: Sat, 22 Apr 2023 10:09:12 +0200 [thread overview]
Message-ID: <834c05ee-287d-e5bf-be07-dec0d6f4b4b4@leemhuis.info> (raw)
In-Reply-To: <5fa67291-98d0-c8d5-ca71-5a86b9adff41@leemhuis.info>
Lo!
On 21.04.23 11:11, Linux regression tracking (Thorsten Leemhuis) wrote:
>
> Bastien, from the bug report it to me sounds like it might be another
> case caused by 908d325e166 ("HID: logitech-hidpp: Detect hi-res
> scrolling support"), but I might be totally wrong with that (and the
> reporter didn't even explicitly state that it's a regression, but it
> sounds like one). If I got something wrong I apologize in advance.
>
> Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217353 :
Ignore that mail, user in between noticed it's a userspace problem.
Sorry for the noise.
#regzbot resolved: userspace problem according to the reporter
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
prev parent reply other threads:[~2023-04-22 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 9:11 [REGRESSION] Bug 217353 - Logitech MX Anywhere 3 scroll wheel works incorrectly over USB dongle Linux regression tracking (Thorsten Leemhuis)
2023-04-22 8:09 ` Linux regression tracking (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=834c05ee-287d-e5bf-be07-dec0d6f4b4b4@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=benjamin.tissoires@redhat.com \
--cc=hadess@hadess.net \
--cc=jikos@kernel.org \
--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