linux-kernel - Re: [PATCH v1 7/7] ARM: dts: imx: Update i.MXRT1050.dtsi compatibles

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]

Message-Id: <d293e410-223d-4baa-ba6d-65bc11ab1e55@app.fastmail.com>
Date:   Mon, 07 Nov 2022 08:44:21 +0100
From:   "Arnd Bergmann" <arnd@...db.de>
To:     "Jesse Taube" <mr.bossman075@...il.com>,
        "NXP Linux Team" <linux-imx@....com>
Cc:     "Rob Herring" <robh+dt@...nel.org>,
        "Stephen Boyd" <sboyd@...nel.org>,
        "Shawn Guo" <shawnguo@...nel.org>,
        "Pengutronix Kernel Team" <kernel@...gutronix.de>,
        "Fabio Estevam" <festevam@...il.com>, aisheng.dong@....com,
        stefan@...er.ch, "Linus Walleij" <linus.walleij@...aro.org>,
        "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
        "Russell King" <linux@...linux.org.uk>, abel.vesa@....com,
        dev@...xeye.de, "Marcel Ziswiler" <marcel.ziswiler@...adex.com>,
        tharvey@...eworks.com, leoyang.li@....com, fugang.duan@....com,
        "Giulio Benetti" <giulio.benetti@...ettiengineering.com>,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        linux-serial@...r.kernel.org
Subject: Re: [PATCH v1 7/7] ARM: dts: imx: Update i.MXRT1050.dtsi compatibles

On Mon, Nov 7, 2022, at 08:15, Jesse Taube wrote:
> Remove unused compatibles from i.MXRT1050.dtsi.
> Change GPT clock-names to match documentation.
>
> Cc: Giulio Benetti <giulio.benetti@...ettiengineering.com>
> Signed-off-by: Jesse Taube <Mr.Bossman075@...il.com>

Can you make sure your changelog texts explain why you do this?
Are they fundamentally different from the devices you had
claimed to be compatible with that need a different driver,
or are there drivers in the field that bind to the wrong
string first?

       Arnd