Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Raphaël Halimi" <raphael.halimi@gmail.com>,
	"Linux Stable Mailing List" <stable@vger.kernel.org>
Cc: Linux Regressions Mailing List <regressions@lists.linux.dev>,
	Linux Input Mailing List <linux-input@vger.kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jiri Kosina <jikos@jikos.cz>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Mikhail Khvainitski <me@khvoinitsky.org>
Subject: Re: Regression with Lenovo ThinkPad Compact USB Keyboard
Date: Sat, 24 Feb 2024 14:08:53 +0100	[thread overview]
Message-ID: <10022b0c-89c3-43e1-89ba-00e458fe1dfd@leemhuis.info> (raw)
In-Reply-To: <7a5fc584-1520-4e52-9c77-d67a656524c6@gmail.com>

On 24.02.24 11:52, Raphaël Halimi wrote:
> Le 20/02/2024 à 19:12, Raphaël Halimi a écrit :
>> I'll let a few days pass (remember, the bug doesn't happen immediately
>> but only after a varying amount of time) and I'll report here if the
>> spurious middle-clicks happened again or not.
> 
> As promised, here's my report: using the recompiled hid-lenvo module
> without those three patches for more than three days, I didn't
> experience a single spurious middle-click, whereas the in-tree module
> triggered the bug several times a day, and I had to unplug/replug the
> keyboard (or simulate it with a software trick) to get back to a normal
> state.
> 
> So those three patches did introduce this regression after all (as I
> correctly guessed).

Mikhail, do you have any idea what might be wrong here? The three
commits Raphaël mentioned that seem to cause the issue are all yours afaics.

Raphaël: would nevertheless still be good if you could identify which of
the three causes the problem, as then the developers might consider
simply reverting it.

Ciao, Thorsten

  reply	other threads:[~2024-02-24 13:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 11:51 Regression with Lenovo ThinkPad Compact USB Keyboard Raphaël Halimi
2024-02-20 11:35 ` Thorsten Leemhuis
2024-02-20 18:12   ` Raphaël Halimi
2024-02-20 19:05     ` Raphaël Halimi
2024-02-24 10:52     ` Raphaël Halimi
2024-02-24 13:08       ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-02-24 13:51         ` Raphaël Halimi
2024-02-24 16:15           ` Raphaël Halimi
2024-03-04 14:33             ` Linux regression tracking (Thorsten Leemhuis)
2024-03-04 14:52               ` Mikhail Khvoinitsky
2024-03-04 15:07                 ` Raphaël Halimi
2024-03-04 15:12                   ` Mikhail Khvoinitsky
2024-03-04 16:09                     ` Raphaël Halimi
2024-03-12 11:56                       ` Raphaël Halimi
2024-03-12 13:05                         ` Mikhail Khvoinitsky
2024-03-12 13:12                           ` Raphaël Halimi

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=10022b0c-89c3-43e1-89ba-00e458fe1dfd@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jikos@jikos.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=me@khvoinitsky.org \
    --cc=raphael.halimi@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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