linux-kernel - Re: [PATCH 1/3] Input: ads7846 - don't report pressure for ads7845

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <83d8742d-f772-4244-4af7-58d355916427@brickedbrain.com>
Date:   Tue, 24 Jan 2023 09:40:05 +0100
From:   Luca Ellero <luca.ellero@...ckedbrain.com>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.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 23/01/2023 13:25, Andy Shevchenko wrote:
> 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.

Hi Andy,
thank you for your reply.
OK, I will add the initial commit as Fixes: tag and resend all the series.
Regards
Luca Ellero