From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: soc@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL 4/4] ARM: SoC devicetree changes for 6.4
Date: Tue, 25 Apr 2023 22:08:53 +0100 [thread overview]
Message-ID: <305e89e6-dd02-4309-844a-3237723c5707@app.fastmail.com> (raw)
In-Reply-To: <CAHk-=wgMmTo=SL1URex5kQbhwGhfBy541tbNbLXrYniAnTxvew@mail.gmail.com>
On Tue, Apr 25, 2023, at 20:21, Linus Torvalds wrote:
> On Mon, Apr 24, 2023 at 2:06 PM Arnd Bergmann <arnd@arndb.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
prev parent reply other threads:[~2023-04-25 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 20:58 [GIT PULL 0/4] SoC branches " Arnd Bergmann
2023-04-24 20:59 ` [GIT PULL 1/4] ARM: SoC changes " Arnd Bergmann
2023-04-24 21:00 ` [GIT PULL 2/4] ARM: SoC drivers for v6.4 Arnd Bergmann
2023-04-24 21:00 ` [GIT PULL 3/4] ARM: SoC defconfig updates for 6.4 Arnd Bergmann
2023-04-24 21:06 ` [GIT PULL 4/4] ARM: SoC devicetree changes " Arnd Bergmann
2023-04-25 19:21 ` Linus Torvalds
2023-04-25 21:08 ` Arnd Bergmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=305e89e6-dd02-4309-844a-3237723c5707@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®