From: Sasha Levin <sashal@kernel.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Allen Ballway <ballway@chromium.org>,
Jiri Kosina <jkosina@suse.cz>,
jikos@kernel.org, benjamin.tissoires@redhat.com,
groeck@chromium.org, alistair@alistair23.me,
dmitry.torokhov@gmail.com, jk@codeconstruct.com.au,
Jonathan.Cameron@huawei.com, cmo@melexis.com,
u.kleine-koenig@pengutronix.de, linux-input@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 5.15 10/25] HID: multitouch: Add quirks for flipped axes
Date: Mon, 27 Feb 2023 09:59:46 -0500 [thread overview]
Message-ID: <Y/zFYpxtkBmNmFLf@sashalap> (raw)
In-Reply-To: <20230227132300.4a3c3fad@endymion.delvare>
On Mon, Feb 27, 2023 at 01:23:00PM +0100, Jean Delvare wrote:
>Hi Sasha,
>
>On Sun, 26 Feb 2023 21:08:33 -0500, Sasha Levin wrote:
>> From: Allen Ballway <ballway@chromium.org>
>>
>> [ Upstream commit a2f416bf062a38bb76cccd526d2d286b8e4db4d9 ]
>>
>> Certain touchscreen devices, such as the ELAN9034, are oriented
>> incorrectly and report touches on opposite points on the X and Y axes.
>> For example, a 100x200 screen touched at (10,20) would report (90, 180)
>> and vice versa.
>>
>> This is fixed by adding device quirks to transform the touch points
>> into the correct spaces, from X -> MAX(X) - X, and Y -> MAX(Y) - Y.
>>
>> Signed-off-by: Allen Ballway <ballway@chromium.org>
>> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> ---
>> drivers/hid/hid-multitouch.c | 39 ++++++++++++++++++---
>> drivers/hid/hid-quirks.c | 6 ++++
>> drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c | 43 ++++++++++++++++++++++++
>> drivers/hid/i2c-hid/i2c-hid.h | 3 ++
>> 4 files changed, 87 insertions(+), 4 deletions(-)
>> (...)
>
>Second rule of acceptance for stable patches:
>
> - It cannot be bigger than 100 lines, with context.
>
>Clearly not met here.
About a quarter of stable commits in the last 12 months breat the rule
above.
>To me, this commit is something distributions may want to backport if
>their users run are likely to run the affected hardware. But it's out
>of scope for stable kernel branches.
Why? We explicitly call out new device IDs and quirks in the same doc
you quoted the 100 line rule from.
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-02-27 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230227020855.1051605-1-sashal@kernel.org>
2023-02-27 2:08 ` [PATCH AUTOSEL 5.15 04/25] HID: Add Mapping for System Microphone Mute Sasha Levin
2023-02-27 2:08 ` [PATCH AUTOSEL 5.15 10/25] HID: multitouch: Add quirks for flipped axes Sasha Levin
2023-02-27 12:23 ` Jean Delvare
2023-02-27 14:34 ` Greg KH
2023-02-27 14:59 ` Sasha Levin [this message]
2023-02-27 2:08 ` [PATCH AUTOSEL 5.15 21/25] HID: logitech-hidpp: Don't restart communication if not necessary Sasha Levin
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=Y/zFYpxtkBmNmFLf@sashalap \
--to=sashal@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=alistair@alistair23.me \
--cc=ballway@chromium.org \
--cc=benjamin.tissoires@redhat.com \
--cc=cmo@melexis.com \
--cc=dmitry.torokhov@gmail.com \
--cc=groeck@chromium.org \
--cc=jdelvare@suse.de \
--cc=jikos@kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).