[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y858otTEDM1ugI0k@smile.fi.intel.com>
Date: Mon, 23 Jan 2023 14:25:06 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Luca Ellero <luca.ellero@...ckedbrain.com>
Cc: Luca Ellero <l.ellero@...m.it>, dmitry.torokhov@...il.com,
daniel@...que.org, m.felsch@...gutronix.de,
u.kleine-koenig@...gutronix.de, mkl@...gutronix.de,
miquel.raynal@...tlin.com, imre.deak@...ia.com,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] Input: ads7846 - don't report pressure for ads7845
On Mon, Jan 23, 2023 at 09:27:37AM +0100, Luca Ellero wrote:
> On 20/01/2023 16:16, Andy Shevchenko wrote:
> > On Fri, Jan 20, 2023 at 01:45:42PM +0100, Luca Ellero wrote:
> > > ADS7845 doesn't support pressure.
> > > This patch avoids the following error reported by libinput-list-devices:
> >
> > s/This patch avoids/Avoid/
> >
> > (This rule is written in Submitting Patches documentation.)
> >
> > > "ADS7845 Touchscreen: kernel bug: device has min == max on ABS_PRESSURE".
> >
> > Do you need a Fixes tag?
> >
>
> Hi Andy,
> thank you for your reply.
> I haven't found a specific bug report to apply to this patches.
> Could you kindly provide a "Fixes:" tag that I can apply?
The Fixes tag in accordance with the documentation should refer to the commit
in the Git history which brought the problem (regression).
> It's more like this driver has never been tested with ADS7845.
> Maybe the patches should be considered as a new implementation instead than
> a bug fix?
If it's indeed from day 1, then the initial commit can be considered as Fixes
tag, but I leave it to maintainer to decide.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists