public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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: Tue, 18 Nov 2014 21:34:00 +0100	[thread overview]
Message-ID: <20141118213400.7d36384f@lilith> (raw)
In-Reply-To: <20141118135237.GX21184@bill-the-cat>

Hello Tom,

On Tue, 18 Nov 2014 08:52:37 -0500, Tom Rini <trini@ti.com> wrote:
> On Sat, Nov 15, 2014 at 09:27:20PM +0100, Albert ARIBAUD wrote:
> > Hello Paul,
> > 
> > On Thu, 13 Nov 2014 23:16:09 +0100, Paul Kocialkowski
> > <contact@paulk.fr> wrote:
> [snip]
> > > Well I think it makes sense to not call this dead code as long as it
> > > *can be* enabled and used on another supported board (for that matter,
> > > any OMAP3+ board will indeed do).
> > 
> > If no board is calling this code right now, that is because none needs
> > it. If none needs it, then it has no reason to be added. The day some
> > board needs this code, the patch to add this code can be submitted
> > along with the patch that calls this code.
> > 
> > > This is very different from e.g. the regulator code that I submitted,
> > > which is only relevant for devices with that particular piece of
> > > hardware (so far, none supported by U-Boot). So it makes sense to submit
> > > that regulator patch only along with support for a board that uses it.
> > 
> > I don't see the difference.
> 
> But this is where I see a difference, "tomorrow".  Setting this, or not
> setting this new behavior is a Kconfig "choice" (in Kconfig-speak).  We
> do not need a defconfig in-tree for every single possible choice since
> at some point we'll do like other Kconfig-based projects and have
> randconfig builds possible to cover "odd" choices, along with
> allyesconfig and allnoconfig to cover the things which people clearly
> need _somewhere_ (and feel the (good!) need to post them in public to
> help others) but may not be able to post the whole board port (not the
> case here per-se but see the various RTC drivers that get posted from
> time to time).

I still don't agree, as a Kconfig option is no different from any
other addition, so I consider that we should only introduce a Kconfig
choice because/when it is needed, not just because it could be needed;
but you're the boss.

> -- 
> Tom

Amicalement,
-- 
Albert.

      reply	other threads:[~2014-11-18 20:34 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
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 [this message]

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=20141118213400.7d36384f@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