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: <ef5d4f48-71b9-2d5c-37f4-7a029a32a41b@gmail.com>
Date:   Mon, 7 Nov 2022 10:09:55 -0500
From:   Jesse Taube <mr.bossman075@...il.com>
To:     Arnd Bergmann <arnd@...db.de>, 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 11/7/22 02:44, Arnd Bergmann wrote:
> 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?
Yes, sorry I wasn't clear.
> Are they fundamentally different from the devices you had
> claimed to be compatible with that need a different driver,
UART and SDHC had drivers added which are better fit.
The GPT binds to imx6dl which is also the same as imx6sl.
> or are there drivers in the field that bind to the wrong
> string first?
I don't understand?

Thanks,
Jesse Taube
> 
>        Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ