From: Shawn Guo <shawnguo@kernel.org>
To: Joseph Guo <qijian.guo@nxp.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>,
Justin Jiang <justin.jiang@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
qijian.guo@oss.nxp.com, Daniel Baluta <daniel.baluta@nxp.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Francesco Valla <francesco@valla.it>,
Tom Zheng <haidong.zheng@nxp.com>,
Steven Yang <steven.yang@nxp.com>, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v3 0/2] Add FRDM i.MX 91 Development board support
Date: Wed, 31 Dec 2025 11:05:37 +0800 [thread overview]
Message-ID: <aVSTARNDcNqvam1f@dragon> (raw)
In-Reply-To: <20251230-imx91_frdm-v3-0-60cac61c96ec@nxp.com>
On Tue, Dec 30, 2025 at 04:58:52PM +0900, Joseph Guo wrote:
> Joseph Guo (2):
> dt-bindings: arm: imx Add FRDM-IMX91 board
Subject prefix "dt-bindings: arm: fsl: " might be better.
Fixed it up and applied both patches, thanks!
Shawn
> arm64: dts: freescale: Add FRDM-IMX91 basic support
prev parent reply other threads:[~2025-12-31 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 7:58 [PATCH v3 0/2] Add FRDM i.MX 91 Development board support Joseph Guo
2025-12-30 7:58 ` [PATCH v3 1/2] dt-bindings: arm: imx Add FRDM-IMX91 board Joseph Guo
2025-12-30 7:58 ` [PATCH v3 2/2] arm64: dts: freescale: Add FRDM-IMX91 basic support Joseph Guo
2025-12-31 3:05 ` Shawn Guo [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=aVSTARNDcNqvam1f@dragon \
--to=shawnguo@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco@valla.it \
--cc=haidong.zheng@nxp.com \
--cc=imx@lists.linux.dev \
--cc=justin.jiang@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qijian.guo@nxp.com \
--cc=qijian.guo@oss.nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=steven.yang@nxp.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;
as well as URLs for NNTP newsgroup(s).