From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v2] common/memsize.c: Increase save array for supporting memory size > 4GB
Date: Wed, 11 Jul 2018 08:50:19 -0400 [thread overview]
Message-ID: <20180711125019.GI27264@bill-the-cat> (raw)
In-Reply-To: <f6771f36-cae2-6f49-8169-c3351eafc433@denx.de>
On Wed, Jul 11, 2018 at 02:48:34PM +0200, Marek Vasut wrote:
> On 07/11/2018 02:42 PM, Tom Rini wrote:
> > On Wed, Jun 20, 2018 at 03:06:20PM +0800, tien.fong.chee at intel.com wrote:
> >
> >> From: Tien Fong Chee <tien.fong.chee@intel.com>
> >>
> >> In ARM 64-bits, memory size can be supported is more than 4GB,
> >> hence increasing save array is needed to cope with testing larger memory.
> >>
> >> Signed-off-by: Tien Fong Chee <tien.fong.chee@intel.com>
> >
> > Applied to u-boot/master, thanks!
>
> There were review comments on this patch which were not addressed,
> please drop.
I thought I had put them in my message here, sorry. I agree with Tien
that we should fix the issue we have now and address the enhancement in
a follow up patch.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180711/c5ba83a2/attachment.sig>
prev parent reply other threads:[~2018-07-11 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 7:06 [U-Boot] [PATCH v2] common/memsize.c: Increase save array for supporting memory size > 4GB tien.fong.chee at intel.com
2018-06-21 4:34 ` Marek Vasut
2018-06-21 6:31 ` Chee, Tien Fong
2018-06-23 3:29 ` Marek Vasut
2018-07-02 13:51 ` Chee, Tien Fong
2018-07-11 12:42 ` [U-Boot] [U-Boot, " Tom Rini
2018-07-11 12:48 ` Marek Vasut
2018-07-11 12:50 ` Tom Rini [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=20180711125019.GI27264@bill-the-cat \
--to=trini@konsulko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox