From: Shawn Guo <shawnguo@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V2 0/5] binding: imx8m: add IOMUXC GPR
Date: Mon, 9 Jan 2023 16:52:15 +0800 [thread overview]
Message-ID: <20230109085214.GI18301@T480> (raw)
In-Reply-To: <20230104002545.3473598-1-peng.fan@oss.nxp.com>
On Wed, Jan 04, 2023 at 08:25:40AM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> V2:
> Update nodename to syscon in patch 3
> Add A-b/R-b tag
>
> Add binding doc for i.MX8M, update dts to match binding doc.
> This is effort for ARM System-Ready 2.0 certification
>
> Peng Fan (5):
> dt-bindings: soc: imx: add IOMUXC GPR support
> arm64: dts: imx8mq: correct iomuxc-gpr compatible
> arm64: dts: imx8mm: correct iomuxc-gpr compatible
> arm64: dts: imx8mn: update iomuxc-gpr node name
> arm64: dts: imx8mp: use syscon for iomuxc-gpr
Applied all, thanks!
prev parent reply other threads:[~2023-01-09 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 0:25 [PATCH V2 0/5] binding: imx8m: add IOMUXC GPR Peng Fan (OSS)
2023-01-04 0:25 ` [PATCH V2 1/5] dt-bindings: soc: imx: add IOMUXC GPR support Peng Fan (OSS)
2023-01-04 0:25 ` [PATCH V2 2/5] arm64: dts: imx8mq: correct iomuxc-gpr compatible Peng Fan (OSS)
2023-01-04 0:25 ` [PATCH V2 3/5] arm64: dts: imx8mm: " Peng Fan (OSS)
2023-01-04 0:25 ` [PATCH V2 4/5] arm64: dts: imx8mn: update iomuxc-gpr node name Peng Fan (OSS)
2023-01-04 0:25 ` [PATCH V2 5/5] arm64: dts: imx8mp: use syscon for iomuxc-gpr Peng Fan (OSS)
2023-01-09 8:52 ` 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=20230109085214.GI18301@T480 \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).