linux-kernel - Re: [PATCH 0/14] Refactor Ralink Pinctrl and Add Documentation

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, 14 Apr 2022 11:26:01 +0300
From:   Arınç ÜNAL <arinc.unal@...nc9.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Sergio Paracuellos <sergio.paracuellos@...il.com>
Cc:     Luiz Angelo Daros de Luca <luizluca@...il.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        Matthias Brugger <matthias.bgg@...il.com>,
        erkin.bozoglu@...ont.com,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>, linux-arm-kernel@...ts.infradead.org,
        "moderated list:ARM/Mediatek SoC support" 
        <linux-mediatek@...ts.infradead.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        "open list:MIPS" <linux-mips@...r.kernel.org>
Subject: Re: [PATCH 0/14] Refactor Ralink Pinctrl and Add Documentation

On 13/04/2022 18:39, Krzysztof Kozlowski wrote:
> On 13/04/2022 08:36, Sergio Paracuellos wrote:
>> I think you cannot change compatible strings because you have to be
>> compatible with previous stuff. That is the reason why when I
>> refactored all of this stuff from 'arch/mips/ralink' into
>> 'drivers/pinctrl' I maintained the same for all of them and only
>> created one binding for all. I know that these SoCs are mostly used in
>> openWRT and the way of doing things there is that when a new version
>> is released a new dtb is also compiled so I understand the motivation
>> of the change itself. In any case, Rob has the last word here, not me
>> :).
> 
> Breaking other users is usually not accepted, so some good reason would
> be needed here...

As I explained on my response to Sergio, this doesn't necessarily break 
anything.

> 
> 
> Best regards,
> Krzysztof