linux-kernel - Re: [PATCH v5] input/i8042: Rework quirk tables

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 29 Mar 2022 16:41:34 +0200
From:   Werner Sembach <wse@...edocomputers.com>
To:     dmitry.torokhov@...il.com, tiwai@...e.de, mpdesouza@...e.com,
        arnd@...db.de, hdegoede@...hat.com, samuel@...oj.net,
        linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5] input/i8042: Rework quirk tables

Am 29.03.22 um 16:36 schrieb Werner Sembach:
> Revision 5 with some fixes based on feedback by Hans de Goede.
>
> The 1st patch is minor housekeeping.
>
> The 2nd patch merges the tables together. Minor fixes in 5th revision and
> no more duplication of ASUS devices
>
> The 3rd patch add optional debug output to see which quirks get applied. In
> 5th revision this no longer breaks compilation on non x86 platforms.
>
> The 4th patch adds a list of Clevo devices that need multiple quirks.
> With the reworked table they don't need to be inserted multiple times now,
> which was required in v1 and v2 of this patch.
>
> I also included the extra quirk for the Clevo NS7xMU, which was a separate
> patch before.
>
> The added Clevo devices are now only identified by their board name as this
> is the only somewhat reliable string that might not be changed by resellers.
>
>
By accident I sent this patchset except the first patch tagged with v4 also. Just want to add this to avoid confusion
and sorry for the spam.

(For some reason selecting 'n' in git send-email only discards the first mail and does not ask for following patches ...
I have to check my git settings)