linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: "Frank Svendsbøe" <frank.svendsboe@gmail.com>,
	LinuxPPC-dev <linuxppc-dev@lists.ozlabs.org>,
	"Wolfgang Denk" <wd@denx.de>,
	robert.karl.berger@gmail.com
Subject: Re: [PATCH] powerpc/boot: Only build board support files when required.
Date: Tue, 03 Apr 2012 11:26:35 +1000	[thread overview]
Message-ID: <1333416395.30734.70.camel@pasglop> (raw)
In-Reply-To: <20120403010002.GE7481@truffala.fritz.box>

On Tue, 2012-04-03 at 11:00 +1000, David Gibson wrote:
> On Tue, Apr 03, 2012 at 10:55:59AM +1000, Tony Breeds wrote:
> > Currently we build all board files regardless of the final zImage
> > target.  This is sub-optimal (in terms on compilation) and leads to
> > problems in one platform needlessly causing failures for other
> > platforms.
> 
> Um.. I believe the one platform breaking another is actually working
> as intended.  I think Paulus did it this way to stop people breaking
> platforms other than the one they were working on without realising
> it.

But that doesn't make sense to enforce that accross CPU families since
they cannot be built together within a single kernel anyway...

Cheers,
Ben.

  reply	other threads:[~2012-04-03  1:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03  0:55 [PATCH] powerpc/boot: Only build board support files when required Tony Breeds
2012-04-03  1:00 ` David Gibson
2012-04-03  1:26   ` Benjamin Herrenschmidt [this message]
2012-04-03  1:31   ` Tony Breeds
2012-04-03  1:41 ` Stephen Rothwell
2012-04-03  1:55   ` Tony Breeds
2012-04-03  1:57     ` Stephen Rothwell
2012-04-04  1:00 ` [PATCH v2] " Tony Breeds
2012-04-05  3:44 ` [PATCH] " Geoff Levand

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=1333416395.30734.70.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=frank.svendsboe@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=robert.karl.berger@gmail.com \
    --cc=wd@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;
as well as URLs for NNTP newsgroup(s).