From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/3] powerpc: Don't build powernv for other platform defconfigs
Date: Fri, 03 Oct 2014 18:04:59 +1000 [thread overview]
Message-ID: <1412323499.2783.6.camel@concordia> (raw)
In-Reply-To: <20140924163410.4f1ad720@canb.auug.org.au>
On Wed, 2014-09-24 at 16:34 +1000, Stephen Rothwell wrote:
> Hi Michael,
>
> On Wed, 24 Sep 2014 15:57:10 +1000 Michael Ellerman <mpe@ellerman.id.au> wrote:
> >
> > Because powernv arrived after these other platforms, the defconfigs
> > didn't have PPC_POWERNV disabled, and being default y it gets turned on.
>
> Well, that raises the question of why PPC_POWERNV is default y at all?
I think that makes sense. With a bare config, you want all the platforms that
can be built to build, so that the kernel you produce is able to boot on as
many things as possible.
If you want a stripped down config for a particular target then we have
defconfigs that do that.
cheers
prev parent reply other threads:[~2014-10-03 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 5:57 [PATCH 1/3] powerpc: Don't build powernv for other platform defconfigs Michael Ellerman
2014-09-24 5:57 ` [PATCH 2/3] powerpc: Enable CONFIG_CRASH_DUMP=y for ppc64_defconfig Michael Ellerman
2014-09-24 5:57 ` [PATCH 3/3] powerpc/kdump: crash_dump.c needs to include io.h Michael Ellerman
2014-09-24 6:36 ` Stephen Rothwell
2014-10-03 8:04 ` Michael Ellerman
2014-09-24 6:34 ` [PATCH 1/3] powerpc: Don't build powernv for other platform defconfigs Stephen Rothwell
2014-10-03 8:04 ` Michael Ellerman [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=1412323499.2783.6.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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).