From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] fastboot: sparse: resync common/image-sparse.c (part 2)
Date: Wed, 1 Jun 2016 10:40:32 +0200 [thread overview]
Message-ID: <20160601084032.GS4908@lukather> (raw)
In-Reply-To: <1463792758-24338-4-git-send-email-srae@broadcom.com>
On Fri, May 20, 2016 at 06:05:56PM -0700, Steve Rae wrote:
> - update fastboot_okay() and fastboot_fail()
>
> This file originally came from upstream code.
>
> While retaining the storage abstraction feature, this is the second
> set of the changes required to resync with the
> cmd_flash_mmc_sparse_img()
> in the file
> aboot.c
> from
> https://us.codeaurora.org/cgit/quic/la/kernel/lk/plain/app/aboot/aboot.c?h=LE.BR.1.2.1
Why is this needed?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- 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/20160601/50bc9bb8/attachment.sig>
next prev parent reply other threads:[~2016-06-01 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 1:05 [U-Boot] [PATCH 0/5] Update fastboot sparse image handling Steve Rae
2016-05-21 1:05 ` [U-Boot] [PATCH 1/5] fastboot: sparse: remove session-id logic Steve Rae
2016-05-21 1:05 ` [U-Boot] [PATCH 2/5] fastboot: sparse: resync common/image-sparse.c (part 1) Steve Rae
2016-06-01 7:33 ` Maxime Ripard
2016-05-21 1:05 ` [U-Boot] [PATCH 3/5] fastboot: sparse: resync common/image-sparse.c (part 2) Steve Rae
2016-06-01 8:40 ` Maxime Ripard [this message]
2016-05-21 1:05 ` [U-Boot] [PATCH 4/5] fastboot: sparse: implement reserve() Steve Rae
2016-05-21 1:05 ` [U-Boot] [PATCH 5/5] fastboot: sparse: improve CHUNK_TYPE_FILL write performance Steve Rae
2016-05-31 17:57 ` [U-Boot] [PATCH 0/5] Update fastboot sparse image handling Steve Rae
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=20160601084032.GS4908@lukather \
--to=maxime.ripard@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox