linux-kernel - Re: [PATCH v2 1/6] ARM: dts: tacoma: Fix node vs reg mismatch for flash memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 19 Nov 2020 05:16:40 +0000
From:   Joel Stanley <joel@....id.au>
To:     Andrew Jeffery <andrew@...id.au>
Cc:     Rob Herring <robh+dt@...nel.org>,
        devicetree <devicetree@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        linux-aspeed <linux-aspeed@...ts.ozlabs.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/6] ARM: dts: tacoma: Fix node vs reg mismatch for
 flash memory

On Thu, 22 Oct 2020 at 01:48, Andrew Jeffery <andrew@...id.au> wrote:
>
> The mismatch lead to a miscalculation of regions in another patch, and
> shouldn't be mismatched anyway, so make them consistent.
>
> Signed-off-by: Andrew Jeffery <andrew@...id.au>

Fixes: 575640201e66 ("ARM: dts: aspeed: tacoma: Use 64MB for firmware memory")
Reviewed-by: Joel Stanley <joel@....id.au>

> ---
>  arch/arm/boot/dts/aspeed-bmc-opp-tacoma.dts | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/aspeed-bmc-opp-tacoma.dts b/arch/arm/boot/dts/aspeed-bmc-opp-tacoma.dts
> index 4d070d6ba09f..e86c22ce6d12 100644
> --- a/arch/arm/boot/dts/aspeed-bmc-opp-tacoma.dts
> +++ b/arch/arm/boot/dts/aspeed-bmc-opp-tacoma.dts
> @@ -26,7 +26,7 @@ reserved-memory {
>                 #size-cells = <1>;
>                 ranges;
>
> -               flash_memory: region@...00000 {
> +               flash_memory: region@...00000 {
>                         no-map;
>                         reg = <0xb8000000 0x4000000>; /* 64M */
>                 };
> --
> 2.25.1
>