linux-kernel - Re: [PATCH] pinctrl/amd: Add device HID for new AMD GPIO controller

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:   Thu, 20 May 2021 02:14:34 +0200
From:   Maximilian Luz <luzmaximilian@...il.com>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        stable <stable@...r.kernel.org>, Sachi King <nakato@...ato.io>
Subject: Re: [PATCH] pinctrl/amd: Add device HID for new AMD GPIO controller

On 20/05/2021 01:50, Linus Walleij wrote:
> On Wed, May 12, 2021 at 11:03 PM Maximilian Luz <luzmaximilian@...il.com> wrote:
> 
>> Add device HID AMDI0031 to the AMD GPIO controller driver match table.
>> This controller can be found on Microsoft Surface Laptop 4 devices and
>> seems similar enough that we can just copy the existing AMDI0030 entry.
>>
>> Cc: <stable@...r.kernel.org> # 5.10+
> 
> Why? It's hardly a regression?

Because that ID is already in use on the Surface Laptop 4 and
potentially other AMD-based laptops that are already available for
purchase. Not having it in stable means that people may have to deal
with some things not working (as this may prevent other drivers relying
on GPIOs from working) until 5.14 is available on their distribution of
choice.

Given the size of this change, I hardly think that's necessary. Which
is, I believe, also why the stable-kernel-rules doc points out that new
device IDs are (generally) allowed.

Regards,
Max