From: Marco Felsch <m.felsch@pengutronix.de>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
devicetree@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
kernel@pengutronix.de, festevam@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/5] arm64: dts: imx8mp: use syscon for iomuxc-gpr
Date: Fri, 23 Dec 2022 09:48:08 +0100 [thread overview]
Message-ID: <20221223084808.35eh5o4ne3uwhjeo@pengutronix.de> (raw)
In-Reply-To: <20221223025703.15784-6-peng.fan@oss.nxp.com>
On 22-12-23, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> It is preferred to use syscon per bindind doc
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
Reviewed-by: Marco Felsch <m.felsch@pengutronix.de>
prev parent reply other threads:[~2022-12-23 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 2:56 [PATCH 0/5] binding: imx8m: add IOMUXC GPR Peng Fan (OSS)
2022-12-23 2:56 ` [PATCH 1/5] dt-bindings: soc: imx: add IOMUXC GPR support Peng Fan (OSS)
2022-12-26 18:49 ` Rob Herring
2022-12-23 2:57 ` [PATCH 2/5] arm64: dts: imx8mq: correct iomuxc-gpr compatible Peng Fan (OSS)
2022-12-23 8:48 ` Marco Felsch
2022-12-23 2:57 ` [PATCH 3/5] arm64: dts: imx8mm: " Peng Fan (OSS)
2022-12-23 8:47 ` Marco Felsch
2022-12-23 2:57 ` [PATCH 4/5] arm64: dts: imx8mn: update iomuxc-gpr node name Peng Fan (OSS)
2022-12-23 8:48 ` Marco Felsch
2022-12-23 2:57 ` [PATCH 5/5] arm64: dts: imx8mp: use syscon for iomuxc-gpr Peng Fan (OSS)
2022-12-23 8:48 ` Marco Felsch [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=20221223084808.35eh5o4ne3uwhjeo@pengutronix.de \
--to=m.felsch@pengutronix.de \
--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 \
--cc=shawnguo@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).