From: Steve Rae <srae@broadcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 0/4] Implement "sparse format" for fastboot
Date: Sat, 23 Aug 2014 10:38:59 -0700 [thread overview]
Message-ID: <1408815543-4591-1-git-send-email-srae@broadcom.com> (raw)
This series implements the "sparse format" file handling for fastboot.
- [1/4] brings in the pristine file "aboot.c"
- [2/4] deletes all unnecessary functions in "aboot.c"
- [3/4] is a simple cleanup of "aboot.c"
- [4/4] provides the implementation of "aboot.c" suitable for U-Boot
NOTE:
The original license in "aboot.c" does not exactly match
the wording in the BSD-3-Clause. I propose adding
BSD-3L-Clause to solve this issue.
----
This series depends on:
http://patchwork.ozlabs.org/patch/379438/
Steve Rae (4):
add code to handle Android sparse image format
update code which handles Android sparse image format
cleanup code which handles the Android sparse image format
implement the Android sparse image format
Licenses/bsd-3L-clause.txt | 24 +++++
common/aboot.c | 217 +++++++++++++++++++++++++++++++++++++++++++++
include/aboot.h | 28 ++++++
include/sparse_defs.h | 7 ++
4 files changed, 276 insertions(+)
create mode 100644 Licenses/bsd-3L-clause.txt
create mode 100644 common/aboot.c
create mode 100644 include/aboot.h
create mode 100644 include/sparse_defs.h
--
1.8.5
next reply other threads:[~2014-08-23 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 17:38 Steve Rae [this message]
2014-08-23 17:39 ` [U-Boot] [PATCH v1 1/4] add code to handle Android sparse image format Steve Rae
2014-08-23 17:39 ` [U-Boot] [PATCH v1 2/4] update code which handles " Steve Rae
2014-08-23 17:39 ` [U-Boot] [PATCH v1 3/4] cleanup code which handles the " Steve Rae
2014-08-28 17:11 ` [U-Boot] [U-Boot, v1, " Tom Rini
2014-08-28 17:24 ` Steve Rae
2014-08-28 17:26 ` Tom Rini
2014-08-23 17:39 ` [U-Boot] [PATCH v1 4/4] implement " 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=1408815543-4591-1-git-send-email-srae@broadcom.com \
--to=srae@broadcom.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