From: Lei Yu <yulei.sh@bytedance.com>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: devicetree@vger.kernel.org, openbmc@lists.ozlabs.org,
Troy Lee <troy_lee@aspeedtech.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [Phishing Risk] [External] [PATCH] ARM: dts: Fix OpenBMC flash layout label addresses
Date: Wed, 5 Jan 2022 13:32:40 +0800 [thread overview]
Message-ID: <CAGm54UF31f4CVzE6FtEVuZ+rkuy1thbMDiw3HrMNLtoeqvCKug@mail.gmail.com> (raw)
In-Reply-To: <20220105003718.19888-1-zev@bewilderbeest.net>
On Wed, Jan 5, 2022 at 8:37 AM Zev Weiss <zev@bewilderbeest.net> wrote:
>
> We've ended up with some inconsistencies between the addresses in the
> DT node labels and the actual offsets of the partitions; this brings
> them back in sync.
>
> Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
> Fixes: 529022738c8e ("ARM: dts: Add OpenBMC flash layout")
> Fixes: 8dec60e7b8d0 ("ARM: dts: aspeed: Grow u-boot partition 64MiB OpenBMC flash layout")
> ---
> arch/arm/boot/dts/openbmc-flash-layout-64.dtsi | 2 +-
> arch/arm/boot/dts/openbmc-flash-layout.dtsi | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/openbmc-flash-layout-64.dtsi b/arch/arm/boot/dts/openbmc-flash-layout-64.dtsi
> index 31f59de5190b..7af41361c480 100644
> --- a/arch/arm/boot/dts/openbmc-flash-layout-64.dtsi
> +++ b/arch/arm/boot/dts/openbmc-flash-layout-64.dtsi
> @@ -28,7 +28,7 @@ rofs@a00000 {
> label = "rofs";
> };
>
> - rwfs@6000000 {
> + rwfs@2a00000 {
> reg = <0x2a00000 0x1600000>; // 22MB
> label = "rwfs";
> };
> diff --git a/arch/arm/boot/dts/openbmc-flash-layout.dtsi b/arch/arm/boot/dts/openbmc-flash-layout.dtsi
> index 6c26524e93e1..b47e14063c38 100644
> --- a/arch/arm/boot/dts/openbmc-flash-layout.dtsi
> +++ b/arch/arm/boot/dts/openbmc-flash-layout.dtsi
> @@ -20,7 +20,7 @@ kernel@80000 {
> label = "kernel";
> };
>
> - rofs@c0000 {
> + rofs@4c0000 {
> reg = <0x4c0000 0x1740000>;
> label = "rofs";
> };
> --
> 2.34.1
>
Reviewed-by: Lei YU <yulei.sh@bytedance.com>
--
BRs,
Lei YU
prev parent reply other threads:[~2022-01-05 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 0:37 [PATCH] ARM: dts: Fix OpenBMC flash layout label addresses Zev Weiss
2022-01-05 0:37 ` Zev Weiss
2022-01-05 5:32 ` Lei Yu [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=CAGm54UF31f4CVzE6FtEVuZ+rkuy1thbMDiw3HrMNLtoeqvCKug@mail.gmail.com \
--to=yulei.sh@bytedance.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=troy_lee@aspeedtech.com \
--cc=zev@bewilderbeest.net \
/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.