All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chee, Tien Fong <tien.fong.chee@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] misc: fs_loader: Add support for initializing block device
Date: Mon, 11 Feb 2019 06:54:11 +0000	[thread overview]
Message-ID: <1549868051.10080.37.camel@intel.com> (raw)
In-Reply-To: <CAPnjgZ3y911GRLAA1XQDPBFgrocfyaaAY-dt+cMU68yJPy4+qQ@mail.gmail.com>

On Fri, 2019-02-01 at 23:06 -0700, Simon Glass wrote:
On Thu, 31 Jan 2019 at 04:34, <tien.fong.chee at intel.com<mailto:tien.fong.chee@intel.com>> wrote:
>
> From: Tien Fong Chee <tien.fong.chee at intel.com<mailto:tien.fong.chee@intel.com>>
>
> Firmware loader would encounter problem if the block device is accessed
> before initializing it. This patch would adding the support of probing
> block device and initializing block before the block device is accessed by
> firmware loader.
>
> Signed-off-by: Tien Fong Chee <tien.fong.chee at intel.com<mailto:tien.fong.chee@intel.com>>
>
> ---
>
> changes in v4
> - Removed header mmc.h
> - Dropped extra blank line
>
> changes in v3:
> - Initializing block device through probing the blk device
>
> changes in v2:
> - Initializing MMC through probing the blk device
> ---
>  drivers/misc/fs_loader.c | 23 +++++++++++++++++++++++
>  1 file changed, 23 insertions(+)

Reviewed-by: Simon Glass <sjg at chromium.org<mailto:sjg@chromium.org>>

(I'm not sure you need to check for DM being enabled, but OK)
Thanks. No strong opinion on this :) .

  reply	other threads:[~2019-02-11  6:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 11:34 [U-Boot] [PATCH v4] misc: fs_loader: Add support for initializing block device tien.fong.chee at intel.com
2019-02-02  6:06 ` Simon Glass
2019-02-11  6:54   ` Chee, Tien Fong [this message]
2019-04-24 13:21 ` [U-Boot] [U-Boot, " Tom Rini

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=1549868051.10080.37.camel@intel.com \
    --to=tien.fong.chee@intel.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.