From: Luca Ellero <luca.ellero@brickedbrain.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Luca Ellero <l.ellero@asem.it>
Cc: dmitry.torokhov@gmail.com, daniel@zonque.org,
m.felsch@pengutronix.de, u.kleine-koenig@pengutronix.de,
mkl@pengutronix.de, miquel.raynal@bootlin.com,
imre.deak@nokia.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ads7846: don't report pressure for ads7845
Date: Wed, 30 Nov 2022 09:25:10 +0100 [thread overview]
Message-ID: <714c731c-2d46-aa39-a134-c41077ed7e0c@brickedbrain.com> (raw)
In-Reply-To: <Y4Yx9o4z9+nhHfLa@smile.fi.intel.com>
On 29/11/2022 17:23, Andy Shevchenko wrote:
> On Tue, Nov 29, 2022 at 04:19:57PM +0100, Luca Ellero wrote:
>> ADS7845 doesn't support pressure.
>> This patch avoids the following error reported by libinput-list-devices:
>> "ADS7845 Touchscreen: kernel bug: device has min == max on ABS_PRESSURE".
>
> Fixes tag?
>
> If you run
>
> git log --no-merges -- drivers/input/touchscreen/ads7846.c
>
> you can get what prefix should be for these patches.
>
Hi Andy,
thank you for your comments.
I will fix the patches and resend.
Regards
--
Luca Ellero
next prev parent reply other threads:[~2022-11-30 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 15:19 [PATCH 0/3 RESEND] ads7846: fix support for ADS7845 Luca Ellero
2022-11-29 15:19 ` [PATCH 1/3] ads7846: don't report pressure for ads7845 Luca Ellero
2022-11-29 16:23 ` Andy Shevchenko
2022-11-30 8:25 ` Luca Ellero [this message]
2022-11-29 15:19 ` [PATCH 2/3] ads7846: always set last command to PWRDOWN Luca Ellero
2022-11-29 16:24 ` Andy Shevchenko
2022-11-29 15:19 ` [PATCH 3/3] ads7846: don't check penirq immediately for 7845 Luca Ellero
2022-11-29 16:24 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2022-07-14 8:43 [PATCH 0/3] ads7846: fix support for ADS7845 Luca Ellero
2022-07-14 8:43 ` [PATCH 1/3] ads7846: don't report pressure for ads7845 Luca Ellero
2022-07-14 11:32 ` Andy Shevchenko
2022-07-15 14:36 ` Luca Ellero
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=714c731c-2d46-aa39-a134-c41077ed7e0c@brickedbrain.com \
--to=luca.ellero@brickedbrain.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel@zonque.org \
--cc=dmitry.torokhov@gmail.com \
--cc=imre.deak@nokia.com \
--cc=l.ellero@asem.it \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=miquel.raynal@bootlin.com \
--cc=mkl@pengutronix.de \
--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).