From: Florian Fainelli <f.fainelli@gmail.com>
To: Aurelien Jarno <aurelien@aurel32.net>,
Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Olof Johansson <olof@lixom.net>, Rob Herring <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
devicetree@vger.kernel.org, Phil Elwell <phil@raspberrypi.com>,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org, soc@kernel.org
Subject: Re: [PATCH RESEND 0/2] arm/arm64: dts: Enable device-tree overlay support for RPi devices
Date: Wed, 18 May 2022 12:52:04 -0700 [thread overview]
Message-ID: <2cfbf1a0-2cef-057d-dce4-13ee50c626d7@gmail.com> (raw)
In-Reply-To: <20220427233607.1225419-1-aurelien@aurel32.net>
On 4/27/2022 4:36 PM, Aurelien Jarno wrote:
> This patchset changes the generation of the Raspberry Pi devices DTB
> files to improve the support for out-of-tree device-tree overlays, like
> it has recently been done for the Nvidia SoCs.
>
> I personally only need that for arm64, but I have added a similar patch
> to do the same on arm.
This looks good to me, Rob, does that approach work for you?
--
Florian
next prev parent reply other threads:[~2022-05-18 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 23:36 [PATCH RESEND 0/2] arm/arm64: dts: Enable device-tree overlay support for RPi devices Aurelien Jarno
2022-04-27 23:36 ` [PATCH RESEND 1/2] arm64: dts: broadcom: " Aurelien Jarno
2022-04-27 23:36 ` [PATCH RESEND 2/2] arm: dts: " Aurelien Jarno
2022-05-18 19:52 ` Florian Fainelli [this message]
2022-07-06 20:51 ` [PATCH RESEND 0/2] arm/arm64: " Aurelien Jarno
2023-06-27 1:56 ` Moessbauer Felix
2023-06-27 5:59 ` Stefan Wahren
2023-06-27 6:52 ` Moessbauer Felix
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=2cfbf1a0-2cef-057d-dce4-13ee50c626d7@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arnd@arndb.de \
--cc=aurelien@aurel32.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--cc=olof@lixom.net \
--cc=phil@raspberrypi.com \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=stefan.wahren@i2se.com \
/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