From: Shawn Guo <shawnguo@kernel.org>
To: Li Yang <leoyang.li@nxp.com>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] ARM: dts: ls1021a: remove "simple-bus" compatible from ifc node
Date: Sun, 10 Apr 2022 15:27:45 +0800 [thread overview]
Message-ID: <20220410072745.GN129381@dragon> (raw)
In-Reply-To: <20220322022818.9860-1-leoyang.li@nxp.com>
On Mon, Mar 21, 2022 at 09:28:13PM -0500, Li Yang wrote:
> The binding of ifc device has been updated. Update dts to match
> accordingly.
>
> Signed-off-by: Li Yang <leoyang.li@nxp.com>
I only received patches #1, #2, #4 and #5, while it claims there are 6
patches in the series.
Shawn
> ---
> arch/arm/boot/dts/ls1021a.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/ls1021a.dtsi b/arch/arm/boot/dts/ls1021a.dtsi
> index 2e69d6eab4d1..52835d3dfa1b 100644
> --- a/arch/arm/boot/dts/ls1021a.dtsi
> +++ b/arch/arm/boot/dts/ls1021a.dtsi
> @@ -123,7 +123,7 @@ msi2: msi-controller@1570e08 {
> };
>
> ifc: ifc@1530000 {
> - compatible = "fsl,ifc", "simple-bus";
> + compatible = "fsl,ifc";
> reg = <0x0 0x1530000 0x0 0x10000>;
> interrupts = <GIC_SPI 75 IRQ_TYPE_LEVEL_HIGH>;
> status = "disabled";
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-04-10 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 2:28 [PATCH 1/6] ARM: dts: ls1021a: remove "simple-bus" compatible from ifc node Li Yang
2022-03-22 2:28 ` [PATCH 2/6] arm64: dts: " Li Yang
2022-03-22 2:28 ` [PATCH 3/6] powerpc/mpc85xx: " Li Yang
2022-03-22 2:28 ` [PATCH 4/6] ARM: dts: update ifc node name to be memory-controller Li Yang
2022-03-22 2:28 ` [PATCH 5/6] arm64: dts: freescale: " Li Yang
2022-03-22 2:28 ` [PATCH 6/6] powerpc/fsl: " Li Yang
2022-04-10 7:27 ` Shawn Guo [this message]
2022-04-27 21:26 ` [PATCH 1/6] ARM: dts: ls1021a: remove "simple-bus" compatible from ifc node Leo Li
2022-05-05 0:50 ` Shawn Guo
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=20220410072745.GN129381@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).