From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2] spl: MMC U-Boot image load from raw partition
Date: Sun, 9 Nov 2014 01:12:51 +0100 [thread overview]
Message-ID: <20141109011251.528415d5@lilith> (raw)
In-Reply-To: <1415485384.2838.13.camel@aldrin>
Hello Paul,
On Sat, 08 Nov 2014 23:23:04 +0100, Paul Kocialkowski
<contact@paulk.fr> wrote:
> Le samedi 08 novembre 2014 ? 23:19 +0100, Albert ARIBAUD a ?crit :
> > Hello Paul,
> >
> > On Sat, 8 Nov 2014 23:14:54 +0100, Paul Kocialkowski
> > <contact@paulk.fr> wrote:
> > > This is a first attempt at adding support for U-Boot image load
> > > from raw partitions. It does not support OS boot as I cannot test
> > > it on my current setup.
> > >
> > > This is going to be useful for the Optimus Black port (please do
> > > not consider this as dead code because no board is using it right
> > > now, there will be one soon)!
> >
> > Well... Why don't you just post these two patches a little later, as
> > part of the upcoming series which will add support for the Optimus
> > Black?
>
> The honest answer here is that I don't think I'll have time to handle
> having the patches reviewed all at once and that I prefer to do things
> step by step, week after week (work on the next thing when the
> previous piece is ready or nearly so). Things are independent enough
> for this to work.
My own honest answer in turn is that potential reviewers of your code
may not think they'll have time to look at code which they cannot
assess because they don't know how it is (going to be) called.
If you feel you cannot handle reviews of the whole set all at once,
then it seems to me the problem is yours to solve: post the whole
series, let the whole review happen, and then just look at the comments
for each patch in turn at your own pace.
This way you avoid posting dead code *and* you get to handle patch
reviews piecewise as you would like.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-11-09 0:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 22:14 [U-Boot] [PATCH 0/2] spl: MMC U-Boot image load from raw partition Paul Kocialkowski
2014-11-08 22:14 ` [U-Boot] [PATCH 1/2] MMC SD fs boot partition config coding style and proper description Paul Kocialkowski
2014-11-10 18:46 ` Tom Rini
2014-12-08 21:41 ` [U-Boot] [U-Boot, " Tom Rini
2014-11-08 22:14 ` [U-Boot] [PATCH 2/2] spl: MMC U-Boot image load from raw partition Paul Kocialkowski
2014-11-10 18:46 ` Tom Rini
2014-12-08 21:41 ` [U-Boot] [U-Boot, " Tom Rini
2014-11-08 22:19 ` [U-Boot] [PATCH 0/2] " Albert ARIBAUD
2014-11-08 22:23 ` Paul Kocialkowski
2014-11-09 0:12 ` Albert ARIBAUD [this message]
2014-11-10 18:46 ` Tom Rini
2014-11-13 11:16 ` Albert ARIBAUD
2014-11-13 22:16 ` Paul Kocialkowski
2014-11-15 20:27 ` Albert ARIBAUD
2014-11-18 13:52 ` Tom Rini
2014-11-18 20:34 ` Albert ARIBAUD
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=20141109011251.528415d5@lilith \
--to=albert.u.boot@aribaud.net \
--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