[PATCH 2/7] global_data.h: Change ram_top type to phys_addr_t

[Simon Glass]

Hi Bin,

On Sat, 30 Jan 2021 at 03:14, Bin Meng <bmeng.cn at gmail.com> wrote:
>
> Hi Simon,
>
> On Sat, Jan 30, 2021 at 1:48 AM Simon Glass <sjg at chromium.org> wrote:
> >
> > Hi Bin,
> >
> > On Sat, 23 Jan 2021 at 19:03, Simon Glass <sjg at chromium.org> wrote:
> > >
> > > On Thu, 21 Jan 2021 at 08:00, Bin Meng <bmeng.cn at gmail.com> wrote:
> > > >
> > > > From: Bin Meng <bin.meng at windriver.com>
> > > >
> > > > It's possible to have ram_top above 4 GiB in a 32-bit system, hence
> > > > we need to declare ram_top as `phys_addr_t`.
> > > >
> > > > Signed-off-by: Bin Meng <bin.meng at windriver.com>
> > > > ---
> > > >
> > > >  include/asm-generic/global_data.h | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > Reviewed-by: Simon Glass <sjg at chromium.org>
> >
> > This patch causes build warnings...can you please take a look?
> >
> > https://gitlab.denx.de/u-boot/custodians/u-boot-dm/-/jobs/213226
>
> That's strange. I did run Azure before I posted this series, and Azure
> did not report any failure.
>
> See https://dev.azure.com/bmeng/GitHub/_build/results?buildId=307&view=results
>
> Did you apply all patches in this series?

At that link you can see the commit I built...I don't know how to see
the list of previous commits in the web interface but I suppose you
could fetch it and look.

Re the warning, it is there... see here:

https://dev.azure.com/bmeng/f9017223-94f4-4916-a888-4cac5e17223f/_apis/build/builds/307/logs/603

Regards,
Simon