From: Shawn Guo <shawn.gsc@gmail.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"moderated list:ARM/FREESCALE LAYERSCAPE ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH 1/4] arm64: dts: ls1012a: correct the size of dcfg block
Date: Tue, 6 Feb 2024 14:16:26 +0800 [thread overview]
Message-ID: <ZcHOuo7iTQBlHC/2@dragon> (raw)
In-Reply-To: <20240119201035.3124007-1-Frank.Li@nxp.com>
On Fri, Jan 19, 2024 at 03:10:32PM -0500, Frank Li wrote:
> From: Li Yang <leoyang.li@nxp.com>
>
> Correct the size of dcfg block to 4k.
>
> Signed-off-by: Zhang Ying-22455 <ying.zhang22455@nxp.com>
> Signed-off-by: Li Yang <leoyang.li@nxp.com>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
Applied all, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawn.gsc@gmail.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
"moderated list:ARM/FREESCALE LAYERSCAPE ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH 1/4] arm64: dts: ls1012a: correct the size of dcfg block
Date: Tue, 6 Feb 2024 14:16:26 +0800 [thread overview]
Message-ID: <ZcHOuo7iTQBlHC/2@dragon> (raw)
In-Reply-To: <20240119201035.3124007-1-Frank.Li@nxp.com>
On Fri, Jan 19, 2024 at 03:10:32PM -0500, Frank Li wrote:
> From: Li Yang <leoyang.li@nxp.com>
>
> Correct the size of dcfg block to 4k.
>
> Signed-off-by: Zhang Ying-22455 <ying.zhang22455@nxp.com>
> Signed-off-by: Li Yang <leoyang.li@nxp.com>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
Applied all, thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-06 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 20:10 [PATCH 1/4] arm64: dts: ls1012a: correct the size of dcfg block Frank Li
2024-01-19 20:10 ` Frank Li
2024-01-19 20:10 ` [PATCH 2/4] arm64: dts: ls1012a: add big-endian property for PCIe nodes Frank Li
2024-01-19 20:10 ` Frank Li
2024-01-19 20:10 ` [PATCH 3/4] arm64: dts: ls1012a: add gpio for i2c bus recovery Frank Li
2024-01-19 20:10 ` Frank Li
2024-01-19 20:10 ` [PATCH 4/4] arm64: dts: ls1012a: fix DWC3 USB VBUS glitch issue Frank Li
2024-01-19 20:10 ` Frank Li
2024-02-06 6:16 ` Shawn Guo [this message]
2024-02-06 6:16 ` [PATCH 1/4] arm64: dts: ls1012a: correct the size of dcfg block 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=ZcHOuo7iTQBlHC/2@dragon \
--to=shawn.gsc@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.