All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] chromebook_samus: Increase pre-relocation memory
Date: Wed, 26 Sep 2018 14:42:42 +0800	[thread overview]
Message-ID: <CAEUhbmUtkz2kdqBoXTdoT_pMWm0OWDstQLPy6QOCNr_kOWymhg@mail.gmail.com> (raw)
In-Reply-To: <CAEUhbmXQWP9uo7iQCckPJBsr_6OK4WMzTTAS-wv2Qr_6hOxuSQ@mail.gmail.com>

On Tue, Sep 4, 2018 at 5:06 PM Bin Meng <bmeng.cn@gmail.com> wrote:
>
> On Mon, Sep 3, 2018 at 7:02 AM Simon Glass <sjg@chromium.org> wrote:
> >
> > With bootstage now allocating pre-relocation memory the current amount
> > available is insufficient. Increase it a little.
> >
> > Signed-off-by: Simon Glass <sjg@chromium.org>
> > ---
> >
> >  configs/chromebook_samus_defconfig | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
>
> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>

applied to u-boot-x86, thanks!

  reply	other threads:[~2018-09-26  6:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 23:02 [U-Boot] [PATCH 0/4] x86: Fix up some bootstage problems Simon Glass
2018-09-02 23:02 ` [U-Boot] [PATCH 1/4] Enable CONFIG_TIMER_EARLY with bootstage Simon Glass
2018-09-04  9:06   ` Bin Meng
2018-09-26  5:41     ` Simon Glass
2018-09-26  6:39       ` Bin Meng
2018-09-27 13:41         ` Simon Glass
2018-10-02 13:25           ` Bin Meng
2018-10-07  1:29             ` Bin Meng
2018-09-02 23:02 ` [U-Boot] [PATCH 2/4] chromebook_samus: Increase pre-relocation memory Simon Glass
2018-09-04  9:06   ` Bin Meng
2018-09-26  6:42     ` Bin Meng [this message]
2018-09-02 23:02 ` [U-Boot] [PATCH 3/4] binman: Add support for Intel reference code Simon Glass
2018-09-04  9:06   ` Bin Meng
2018-09-26  6:43     ` Bin Meng
2018-09-02 23:02 ` [U-Boot] [PATCH 4/4] Revert "x86: galileo: Fix boot failure" Simon Glass
2018-09-04  9:07   ` Bin Meng
2018-09-26  5:41     ` Simon Glass
2018-09-26  6:40       ` 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=CAEUhbmUtkz2kdqBoXTdoT_pMWm0OWDstQLPy6QOCNr_kOWymhg@mail.gmail.com \
    --to=bmeng.cn@gmail.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 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.