From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/5] fastboot: sparse: resync common/image-sparse.c (part 1)
Date: Wed, 22 Jun 2016 21:36:23 +0200 [thread overview]
Message-ID: <20160622193623.GY26668@lukather> (raw)
In-Reply-To: <CAM7GXokudRs+wsjzj0cTT9+dU3hNtdgC3wQi1AE0Bpa602c9fA@mail.gmail.com>
On Thu, Jun 16, 2016 at 10:29:39AM -0700, Steve Rae wrote:
> On Wed, Jun 15, 2016 at 1:18 AM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:
> >
> > On Tue, Jun 07, 2016 at 11:19:36AM -0700, Steve Rae wrote:
> > > This file originally came from upstream code.
> > >
> > > While retaining the storage abstraction feature, this is the first
> > > 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
> > >
> > > Signed-off-by: Steve Rae <srae@broadcom.com>
> >
> > Again, please split that in several patches to have one patch
> > per-change you're doing.
> >
> > This is just impossible to review.
>
> And I think you just reinforced the point:
> this code was so far away from the original upstream code that it
> is not even recognizable anymore....
I think the only point that was made is that a different bootloader
has a different implementation of the same protocol, just like for any
other protocol.
An implementation relying on a 120 lines switch statement, and a 250
lines functions, that hardcodes the backing storage device.
I'm not sure this is such a good inspiration.
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/20160622/3ac02f06/attachment.sig>
next prev parent reply other threads:[~2016-06-22 19:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 18:19 [U-Boot] [PATCH v2 0/5] Update fastboot sparse image handling Steve Rae
2016-06-07 18:19 ` [U-Boot] [PATCH v2 1/5] fastboot: sparse: remove session-id logic Steve Rae
2016-06-28 1:12 ` [U-Boot] [U-Boot, v2, " Tom Rini
2016-06-07 18:19 ` [U-Boot] [PATCH v2 2/5] fastboot: sparse: resync common/image-sparse.c (part 1) Steve Rae
2016-06-15 8:18 ` Maxime Ripard
2016-06-16 17:29 ` Steve Rae
2016-06-22 19:36 ` Maxime Ripard [this message]
2016-06-22 21:44 ` Tom Rini
2016-06-28 1:12 ` [U-Boot] [U-Boot, v2, " Tom Rini
2016-06-07 18:19 ` [U-Boot] [PATCH v2 3/5] fastboot: sparse: resync common/image-sparse.c (part 2) Steve Rae
2016-06-28 1:12 ` [U-Boot] [U-Boot, v2, " Tom Rini
2016-06-07 18:19 ` [U-Boot] [PATCH v2 4/5] fastboot: sparse: implement reserve() Steve Rae
2016-06-15 8:31 ` Maxime Ripard
2016-06-28 1:12 ` [U-Boot] [U-Boot,v2,4/5] " Tom Rini
2016-06-07 18:19 ` [U-Boot] [PATCH v2 5/5] fastboot: sparse: improve CHUNK_TYPE_FILL write performance Steve Rae
2016-06-15 8:36 ` Maxime Ripard
2016-06-16 17:34 ` Steve Rae
2016-06-16 17:47 ` Steve Rae
2016-06-22 19:39 ` Maxime Ripard
2016-06-28 1:12 ` [U-Boot] [U-Boot, v2, " Tom Rini
2016-06-07 18:36 ` [U-Boot] [PATCH v2 0/5] Update fastboot sparse image handling Sergey Kubushyn
2016-06-07 18:38 ` Steve Rae
2016-06-07 20:20 ` 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=20160622193623.GY26668@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