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 v2 1/6] cbfs: Allow CBFS to be used in SPL
Date: Fri, 16 Aug 2019 22:42:05 +0800	[thread overview]
Message-ID: <CAEUhbmWHxYebgB2WAX9SFKEw9DTLDCVJw4L-qn2W6T6UsE_4vg@mail.gmail.com> (raw)
In-Reply-To: <20190815015615.164307-2-sjg@chromium.org>

On Thu, Aug 15, 2019 at 9:56 AM Simon Glass <sjg@chromium.org> wrote:
>
> Add a new Kconfig option to enable CBFS in SPL. This can be useful when
> the memory-init code is in CBFS.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
> ---
>
> Changes in v2:
> - Fix typo in Kconfig help
>
>  fs/Makefile     |  1 +
>  fs/cbfs/Kconfig | 12 ++++++++++++
>  2 files changed, 13 insertions(+)
>

Tested-by: Bin Meng <bmeng.cn@gmail.com>

  reply	other threads:[~2019-08-16 14:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15  1:56 [U-Boot] [PATCH v2 0/6] cbfs: Allow use before relocation / BSS Simon Glass
2019-08-15  1:56 ` [U-Boot] [PATCH v2 1/6] cbfs: Allow CBFS to be used in SPL Simon Glass
2019-08-16 14:42   ` Bin Meng [this message]
2019-08-18 13:59     ` Bin Meng
2019-08-15  1:56 ` [U-Boot] [PATCH v2 2/6] cbfs: Move declarations above functions Simon Glass
2019-08-16 14:42   ` Bin Meng
2019-08-18 13:59     ` Bin Meng
2019-08-15  1:56 ` [U-Boot] [PATCH v2 3/6] cbfs: Move static variables into a struct Simon Glass
2019-08-15  7:18   ` Bin Meng
2019-08-16 14:43     ` Bin Meng
2019-08-18 13:59       ` Bin Meng
2019-08-15  1:56 ` [U-Boot] [PATCH v2 4/6] cbfs: Move result variable into the struct Simon Glass
2019-08-16 14:43   ` Bin Meng
2019-08-18 13:59     ` Bin Meng
2019-08-15  1:56 ` [U-Boot] [PATCH v2 5/6] cbfs: Add functions to support multiple CBFSs Simon Glass
2019-08-16 14:43   ` Bin Meng
2019-08-18 13:59     ` Bin Meng
2019-08-15  1:56 ` [U-Boot] [PATCH v2 6/6] cbfs: Rename camel-case variables Simon Glass
2019-08-16 14:44   ` Bin Meng
2019-08-18 13:59     ` 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=CAEUhbmWHxYebgB2WAX9SFKEw9DTLDCVJw4L-qn2W6T6UsE_4vg@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.