linux-kernel - Re: [GIT PULL 4/4] ARM: SoC devicetree changes for 6.4

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

Message-Id: <305e89e6-dd02-4309-844a-3237723c5707@app.fastmail.com>
Date:   Tue, 25 Apr 2023 22:08:53 +0100
From:   "Arnd Bergmann" <arnd@...db.de>
To:     "Linus Torvalds" <torvalds@...ux-foundation.org>
Cc:     soc@...nel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL 4/4] ARM: SoC devicetree changes for 6.4

On Tue, Apr 25, 2023, at 20:21, Linus Torvalds wrote:
> On Mon, Apr 24, 2023 at 2:06 PM Arnd Bergmann <arnd@...db.de> wrote:
>>
>> ARM: SoC devicetree changes for 6.4
>
> Hmm. This also has commit e49eabe3e13f ("pinctrl: qcom: Support
> OUTPUT_ENABLE; deprecate INPUT_ENABLE") that doesn't seem to be
> obviously about devicetree changes.
>
> Whatever. I took the pull, but that change looked oddly out of place..

Right, this was a commit that is also in the pinctrl tree, and
Bjorn pulled it into the qcom/dt tree to make sure this can be
properly bisected. As the patch description explains, the driver
did not implement the binding correctly, so changing it like this
at least keeps compatibility in one direction (old DTB with new
kernel) while fixing both the driver and the dts files to work
with the documented binding.

Normally this should not be necessary as long as we keep
compatibility both ways, but I trust that Bjorn was confident
this would not cause problems here.

     Arnd