All of lore.kernel.org
 help / color / mirror / Atom feed
From: erikhakan@gmail.com
To: Rafael Passos <rafael@rcpassos.me>,
	Alexey Zagorodnikov <xglooom@gmail.com>,
	Rafael Passos <rafael@rcpassos.me>,
	lains@riseup.net, hadess@hadess.net, jikos@kernel.org,
	bentiss@kernel.org, Shuah Khan <skhan@linuxfoundation.org>,
	Brigham Campbell <me@brighamcampbell.com>,
	Jori Koolstra <jkoolstra@xs4all.nl>,
	linux-input@vger.kernel.org,
	devnull+greyxor.protonmail.com@kernel.org, k8ie@mcld.eu
Subject: Re: [PATCH] HID: logitech-hidpp: fix hi-res scroll for Bolt-connected MX Master
Date: Mon, 7 Sep 2026 19:46:28 +0200	[thread overview]
Message-ID: <6d7c758f-168f-42b3-b195-b6c2f52f0cf6@gmail.com> (raw)
In-Reply-To: <DL6T82VA1NU5.1R1U7FE0CF6H@rcpassos.me>

Hi again!
This patch works fine on my MX Keys Business. No regressions noted.

It seems then that the earlier patch by Grégoire cause similar regressions to what
Kateřina Medvědová reported when all three interfaces were treated as DJ interfaces
in https://lore.kernel.org/linux-input/345f7347-30a8-4568-a7a6-c70f54a52a8d@mcld.eu/
where she reported e.g. that the mouse became very sensitive as well as some
other issues.

I.e. it seems like this patch is the better approach.

Thanks
Erik

  reply	other threads:[~2026-09-07 17:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04  3:48 [PATCH] HID: logitech-hidpp: fix hi-res scroll for Bolt-connected MX Master Rafael Passos
2026-09-04  4:02 ` sashiko-bot
2026-09-04  7:44 ` Alexey Zagorodnikov
2026-09-04 16:34   ` Erik Håkansson
2026-09-04 17:03     ` Benjamin Tissoires
2026-09-04 18:20       ` Alexey Zagorodnikov
2026-09-04 18:17     ` Alexey Zagorodnikov
2026-09-04 20:21       ` Rafael Passos
2026-09-07 17:46         ` erikhakan [this message]
2026-09-14 10:31 ` Oleksandr Natalenko
2026-09-14 10:51   ` Oleksandr Natalenko
2026-09-22 15:28     ` erikhakan
2026-09-22 16:28       ` Rafael Passos
2026-09-22 16:32     ` Rafael Passos
2026-09-22 20:33       ` Oleksandr Natalenko

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=6d7c758f-168f-42b3-b195-b6c2f52f0cf6@gmail.com \
    --to=erikhakan@gmail.com \
    --cc=bentiss@kernel.org \
    --cc=devnull+greyxor.protonmail.com@kernel.org \
    --cc=hadess@hadess.net \
    --cc=jikos@kernel.org \
    --cc=jkoolstra@xs4all.nl \
    --cc=k8ie@mcld.eu \
    --cc=lains@riseup.net \
    --cc=linux-input@vger.kernel.org \
    --cc=me@brighamcampbell.com \
    --cc=rafael@rcpassos.me \
    --cc=skhan@linuxfoundation.org \
    --cc=xglooom@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.