From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Olof Johansson <olof@lixom.net>, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org, soc@kernel.org
Subject: Re: [PATCH 0/2] arm/arm64: dts: Enable device-tree overlay support for RPi devices
Date: Mon, 22 May 2023 08:22:54 +0200 [thread overview]
Message-ID: <20230522062254.6biyisl4qp7krm3h@pengutronix.de> (raw)
In-Reply-To: <20220410225940.135744-1-aurelien@aurel32.net>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Hello,
On Mon, Apr 11, 2022 at 12:59:38AM +0200, 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.
>
> Aurelien Jarno (2):
> arm64: dts: broadcom: Enable device-tree overlay support for RPi
> devices
> arm: dts: Enable device-tree overlay support for RPi devices
I like these changes,
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Given there was no feedback for >1 year now, I wonder if there are good
reasons against this change, or it just fell through the cracks?!
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-05-22 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 22:59 [PATCH 0/2] arm/arm64: dts: Enable device-tree overlay support for RPi devices Aurelien Jarno
2022-04-10 22:59 ` [PATCH 1/2] arm64: dts: broadcom: " Aurelien Jarno
2023-05-25 7:36 ` Uwe Kleine-König
2022-04-10 22:59 ` [PATCH 2/2] arm: dts: " Aurelien Jarno
2023-05-22 6:22 ` Uwe Kleine-König [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=20230522062254.6biyisl4qp7krm3h@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=arnd@arndb.de \
--cc=aurelien@aurel32.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.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;
as well as URLs for NNTP newsgroup(s).