From: Chee, Tien Fong <tien.fong.chee@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 06/20] common: Generic firmware loader for file system
Date: Tue, 31 Oct 2017 11:50:23 +0000 [thread overview]
Message-ID: <1509450623.2839.9.camel@intel.com> (raw)
In-Reply-To: <9fe984f7-9132-f9a3-3bf7-b9d5c2230247@denx.de>
On Sel, 2017-10-31 at 12:35 +0100, Marek Vasut wrote:
> On 10/31/2017 12:16 PM, Chee, Tien Fong wrote:
> >
> > On Sel, 2017-10-31 at 12:02 +0100, Marek Vasut wrote:
> > >
> > > On 10/31/2017 11:52 AM, tien.fong.chee at intel.com wrote:
> > > >
> > > >
> > > > From: Tien Fong Chee <tien.fong.chee@intel.com>
> > > >
> > > > Generic firmware loader framework contains some common
> > > > functionality
> > > > which is reusable by any specific driver file system firmware
> > > > loader.
> > > > Specific driver file system firmware loader handling can be
> > > > defined
> > > > with both weak function fsloader_preprocess and fs_loading.
> > > >
> > > > Signed-off-by: Tien Fong Chee <tien.fong.chee@intel.com>
> > > Note that this should be sent separately from the SoCFPGA stuff.
> > >
> > This patch separate from SoCFPGA stuff. But, it is required by
> > later
> > patch. FPGA loadfs implemented based on this patch.
> You can note that in the cover letter.
>
Okay.
prev parent reply other threads:[~2017-10-31 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 10:52 [U-Boot] [PATCH v4 06/20] common: Generic firmware loader for file system tien.fong.chee at intel.com
2017-10-31 11:01 ` Marek Vasut
2017-10-31 11:15 ` Chee, Tien Fong
2017-10-31 11:35 ` Marek Vasut
2017-10-31 11:53 ` Chee, Tien Fong
2017-11-01 3:58 ` Chee, Tien Fong
2017-10-31 11:02 ` Marek Vasut
2017-10-31 11:16 ` Chee, Tien Fong
2017-10-31 11:35 ` Marek Vasut
2017-10-31 11:50 ` Chee, Tien Fong [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=1509450623.2839.9.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.