From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot,3/3] mmc: support writing sparse images
Date: Tue, 8 May 2018 13:15:47 -0400 [thread overview]
Message-ID: <20180508171547.GB12235@bill-the-cat.ec.rr.com> (raw)
In-Reply-To: <1522996524-23376-1-git-send-email-jassisinghbrar@gmail.com>
On Fri, Apr 06, 2018 at 12:05:24PM +0530, jassisinghbrar at gmail.com wrote:
> From: Jassi Brar <jaswinder.singh@linaro.org>
>
> Provide an alternate path for sparse-images to be
> written to MMC. For example, via tftp on platforms
> that don't support fastboot protocol. Or when an
> image is to written at some offset, rather than the
> start of a partition.
>
> Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
Applied to u-boot/master, thanks!
--
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/20180508/beda500c/attachment.sig>
next prev parent reply other threads:[~2018-05-08 17:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 6:34 [U-Boot] [PATCH 0/3] Enable mmc to write sparse images jassisinghbrar at gmail.com
2018-04-06 6:34 ` [U-Boot] [PATCH 1/3] fastboot: sparse: remove redundant argument to write_sparse_image jassisinghbrar at gmail.com
2018-05-08 17:15 ` [U-Boot] [U-Boot, " Tom Rini
2018-04-06 6:35 ` [U-Boot] [PATCH 2/3] fastboot: sparse: make write_sparse_image useable for non-fastboot jassisinghbrar at gmail.com
2018-05-08 17:15 ` [U-Boot] [U-Boot, " Tom Rini
2018-04-06 6:35 ` [U-Boot] [PATCH 3/3] mmc: support writing sparse images jassisinghbrar at gmail.com
2018-05-08 17:15 ` Tom Rini [this message]
2018-05-14 13:12 ` [U-Boot] [U-Boot,3/3] " Jassi Brar
2018-05-14 14:46 ` Tom Rini
2018-05-14 16:14 ` Alex Kiernan
2018-05-14 20:50 ` Tom Rini
2018-05-14 21:08 ` Alex Kiernan
2018-05-08 3:59 ` [U-Boot] [PATCH 0/3] Enable mmc to write " Jassi Brar
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=20180508171547.GB12235@bill-the-cat.ec.rr.com \
--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 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.