From: Greg KH <gregkh@linuxfoundation.org>
To: Benjamin Tissoires <bentiss@kernel.org>
Cc: stable@vger.kernel.org, Jiri Kosina <jkosina@suse.com>
Subject: Re: [PATCH 6.12.y] HID: multitouch: fix sticky fingers
Date: Mon, 20 Oct 2025 15:27:41 +0200 [thread overview]
Message-ID: <2025102027-capsule-bottle-6760@gregkh> (raw)
In-Reply-To: <teds5da4vofr4oc2ddlbxxgfidyc5oavagav2ksddkd7jl4ivw@mw554wr4vy4s>
On Mon, Oct 20, 2025 at 02:52:24PM +0200, Benjamin Tissoires wrote:
> On Oct 20 2025, bentiss@kernel.org wrote:
> > From: Benjamin Tissoires <bentiss@kernel.org>
> >
> > commit 46f781e0d151844589dc2125c8cce3300546f92a upstream.
> >
> > The sticky fingers quirk (MT_QUIRK_STICKY_FINGERS) was only considering
> > the case when slots were not released during the last report.
> > This can be problematic if the firmware forgets to release a finger
> > while others are still present.
> >
> > This was observed on the Synaptics DLL0945 touchpad found on the Dell
> > XPS 9310 and the Dell Inspiron 5406.
> >
> > Fixes: 4f4001bc76fd ("HID: multitouch: fix rare Win 8 cases when the touch up event gets missing")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Benjamin Tissoires <bentiss@kernel.org>
> > Signed-off-by: Jiri Kosina <jkosina@suse.com>
> > Signed-off-by: Benjamin Tissoires <bentiss@kernel.org>
> > ---
>
> Greg,
>
> This backport also applies cleanly up to 5.10. Though I'm not sure we
> want to go that far in the history TBH.
>
> Can you also take this version and apply it to 6.1+? (or do you want me
> to send individual rebases for each tree?)
I've taken it back to 5.10.y as-is, thanks!
greg k-h
prev parent reply other threads:[~2025-10-20 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 8:14 FAILED: patch "[PATCH] HID: multitouch: fix sticky fingers" failed to apply to 6.12-stable tree gregkh
2025-10-20 12:43 ` [PATCH 6.12.y] HID: multitouch: fix sticky fingers bentiss
2025-10-20 12:52 ` Benjamin Tissoires
2025-10-20 13:27 ` Greg KH [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=2025102027-capsule-bottle-6760@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bentiss@kernel.org \
--cc=jkosina@suse.com \
--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