From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH 2/7] global_data.h: Change ram_top type to phys_addr_t
Date: Fri, 29 Jan 2021 10:47:52 -0700 [thread overview]
Message-ID: <CAPnjgZ2pVaacE6LzHXKKk4U2pWrzdjoP65WQr+oups=A4J3ASQ@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ3ghiXcv4EE3Ru+g7-DbWZdc1pe0fO=vPtxpzuC66wvpw@mail.gmail.com>
Hi Bin,
On Sat, 23 Jan 2021 at 19:03, Simon Glass <sjg@chromium.org> wrote:
>
> On Thu, 21 Jan 2021 at 08:00, Bin Meng <bmeng.cn@gmail.com> wrote:
> >
> > From: Bin Meng <bin.meng@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@windriver.com>
> > ---
> >
> > include/asm-generic/global_data.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Reviewed-by: Simon Glass <sjg@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
Regards,
Simon
next prev parent reply other threads:[~2021-01-29 17:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 15:00 [PATCH 0/7] Allow booting a 32-bit system with a top memory address beyond 4 GiB Bin Meng
2021-01-21 15:00 ` [PATCH 1/7] riscv: Adjust board_get_usable_ram_top() for 32-bit Bin Meng
2021-01-21 15:00 ` [PATCH 2/7] global_data.h: Change ram_top type to phys_addr_t Bin Meng
2021-01-24 2:03 ` Simon Glass
2021-01-29 17:47 ` Simon Glass [this message]
2021-01-30 10:13 ` Bin Meng
2021-01-30 16:24 ` Simon Glass
2021-01-31 3:40 ` Bin Meng
2021-01-31 3:44 ` Simon Glass
2021-01-31 8:35 ` Bin Meng
2021-01-21 15:00 ` [PATCH 3/7] serial: sifive: Cast dev_read_addr() with uintptr_t Bin Meng
2021-01-21 15:00 ` [PATCH 4/7] fdtdec: Cast prior_stage_fdt_address " Bin Meng
2021-01-24 2:03 ` Simon Glass
2021-01-21 15:00 ` [PATCH 5/7] riscv: Change phys_addr_t and phys_size_t to 64-bit Bin Meng
2021-01-21 15:00 ` [PATCH 6/7] bdinfo: Rename function names to be clearer Bin Meng
2021-01-21 15:00 ` [PATCH 7/7] bdinfo: Change to use bdinfo_print_num_ll() where the number could be 64-bit Bin Meng
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='CAPnjgZ2pVaacE6LzHXKKk4U2pWrzdjoP65WQr+oups=A4J3ASQ@mail.gmail.com' \
--to=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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.