[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=WXW3aApS=c7baxhtfr1Nf-UnBN2s=rEBBkjj4=TCdT+g@mail.gmail.com>
Date: Mon, 13 May 2019 15:48:22 -0700
From: Doug Anderson <dianders@...omium.org>
To: Rob Clark <robdclark@...il.com>
Cc: linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Stephen Boyd <swboyd@...omium.org>,
Rob Clark <robdclark@...omium.org>,
Andy Gross <andy.gross@...aro.org>,
David Brown <david.brown@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 2/3] arm64: dts: qcom: sdm845-cheza: Re-add reserved memory
Hi,
On Thu, May 9, 2019 at 11:44 AM Rob Clark <robdclark@...il.com> wrote:
> From: Douglas Anderson <dianders@...omium.org>
>
> Let's fixup the reserved memory to re-add the things we deleted in
> ("CHROMIUM: arm64: dts: qcom: sdm845-cheza: Temporarily delete
> reserved-mem changes") in a way that plays nicely with the new
> upstream definitions.
The message above makes no sense since that commit you reference isn't
in upstream.
...but in any case, why not squash this in with the previous commit?
> Signed-off-by: Douglas Anderson <dianders@...omium.org>
> Reviewed-by: Stephen Boyd <swboyd@...omium.org>
> Signed-off-by: Rob Clark <robdclark@...omium.org>
Remove Stephen's Reviewed-by. In general reviews that happen in the
Chrome OS gerrit shouldn't be carried over when things are posted
upstream.
> +/* Increase the size from 2MB to 8MB */
> +&rmtfs_mem {
> + reg = <0 0x88f00000 0 0x800000>;
> +};
> +
> +/ {
> + reserved-memory {
> + venus_mem: memory@...00000 {
> + reg = <0 0x96000000 0 0x500000>;
> + no-map;
> + };
> + };
> +};
nit: blank line?
-Doug
Powered by blists - more mailing lists