From: Frank Li <Frank.li@nxp.com>
To: Max Merchel <Max.Merchel@ew.tq-group.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux@ew.tq-group.com, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] ARM: dts: TQMa6UL: modify for use in bootloaders
Date: Wed, 18 Feb 2026 12:03:43 -0500 [thread overview]
Message-ID: <aZXw76CuH9u8csFk@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260218132339.32157-1-Max.Merchel@ew.tq-group.com>
On Wed, Feb 18, 2026 at 02:23:33PM +0100, Max Merchel wrote:
> This series contains modifications for using Linux device trees
> in bootloaders. Changes from U-Boot bootloader are incorporated
> directly into the Linux device trees.
Reviewed-by: Frank Li <Frank.Li@nxp.com>
>
> Max Merchel (4):
> ARM: dts: imx6ul/imx6ull: add boot phase properties
> ARM: dts: imx6ul[l]-tqma6ul[l]: add boot phase properties
> ARM: dts: mba6ulx: add boot phase properties
> ARM: dts: tqma6ul[l]: correct spelling of TQ-Systems
>
> arch/arm/boot/dts/nxp/imx/imx6ul-tqma6ul-common.dtsi | 10 ++++++++++
> arch/arm/boot/dts/nxp/imx/imx6ul-tqma6ul2.dtsi | 1 +
> arch/arm/boot/dts/nxp/imx/imx6ul-tqma6ul2l-mba6ulx.dts | 4 ++--
> arch/arm/boot/dts/nxp/imx/imx6ul-tqma6ul2l.dtsi | 1 +
> arch/arm/boot/dts/nxp/imx/imx6ul-tqma6ulx-common.dtsi | 1 +
> arch/arm/boot/dts/nxp/imx/imx6ul-tqma6ulxl-common.dtsi | 1 +
> arch/arm/boot/dts/nxp/imx/imx6ul.dtsi | 6 ++++++
> arch/arm/boot/dts/nxp/imx/imx6ull-tqma6ull2.dtsi | 1 +
> .../boot/dts/nxp/imx/imx6ull-tqma6ull2l-mba6ulx.dts | 2 +-
> arch/arm/boot/dts/nxp/imx/imx6ull-tqma6ull2l.dtsi | 3 ++-
> arch/arm/boot/dts/nxp/imx/imx6ull.dtsi | 1 +
> arch/arm/boot/dts/nxp/imx/mba6ulx.dtsi | 6 ++++++
> 12 files changed, 33 insertions(+), 4 deletions(-)
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-02-18 17:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 13:23 [PATCH 0/4] ARM: dts: TQMa6UL: modify for use in bootloaders Max Merchel
2026-02-18 13:23 ` [PATCH 1/4] ARM: dts: imx6ul/imx6ull: add boot phase properties Max Merchel
2026-02-18 18:14 ` Fabio Estevam
2026-02-20 12:10 ` Max Merchel
2026-02-20 13:14 ` Max Merchel
2026-02-20 13:46 ` Fabio Estevam
2026-02-18 13:23 ` [PATCH 2/4] ARM: dts: imx6ul[l]-tqma6ul[l]: " Max Merchel
2026-02-18 13:23 ` [PATCH 3/4] ARM: dts: mba6ulx: " Max Merchel
2026-02-18 13:23 ` [PATCH 4/4] ARM: dts: tqma6ul[l]: correct spelling of TQ-Systems Max Merchel
2026-02-18 17:03 ` Frank Li [this message]
2026-02-18 19:44 ` [PATCH 0/4] ARM: dts: TQMa6UL: modify for use in bootloaders Krzysztof Kozlowski
2026-02-19 19:45 ` Frank Li
2026-02-20 9:44 ` Daniel Baluta
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=aZXw76CuH9u8csFk@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=Max.Merchel@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
/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