From: Francesco Dolcini <francesco@dolcini.it>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Input: ilitek_ts_i2c - Fix spurious input events
Date: Wed, 31 Jul 2024 11:26:35 +0200 [thread overview]
Message-ID: <20240731092635.GA32718@francesco-nb> (raw)
In-Reply-To: <20231222183114.30775-1-francesco@dolcini.it>
Hello Dmitry,
On Fri, Dec 22, 2023 at 07:31:12PM +0100, Francesco Dolcini wrote:
> A couple of fixes to prevent spurious events when the data buffer is not the
> expected one.
Any chance you can merge this series or provide feedback on it? This is
open since 10 months now and I would need some help on moving it forward.
Thanks,
Francesco
prev parent reply other threads:[~2024-07-31 9:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 18:31 [PATCH v3 0/2] Input: ilitek_ts_i2c - Fix spurious input events Francesco Dolcini
2023-12-22 18:31 ` [PATCH v3 1/2] Input: ilitek_ts_i2c - avoid wrong input subsystem sync Francesco Dolcini
2024-07-31 18:59 ` Dmitry Torokhov
2023-12-22 18:31 ` [PATCH v3 2/2] Input: ilitek_ts_i2c - add report id message validation Francesco Dolcini
2024-07-31 19:00 ` Dmitry Torokhov
2024-07-31 9:26 ` Francesco Dolcini [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=20240731092635.GA32718@francesco-nb \
--to=francesco@dolcini.it \
--cc=dmitry.torokhov@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).