From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH] powerpc: remove default=y from PMAC and CHRP Kconfigs
Date: Thu, 9 Oct 2008 20:22:24 -0500 [thread overview]
Message-ID: <68168CE9-D17F-4C55-BF0B-0FAFC3672398@kernel.crashing.org> (raw)
In-Reply-To: <18670.42312.827841.167852@cargo.ozlabs.ibm.com>
On Oct 9, 2008, at 7:43 PM, Paul Mackerras wrote:
> Timur Tabi writes:
>
>> I'm waiting for someone to explain to me what's so special about CHRP
>> and PMAC that these two platforms should be enabled by default, when
>> all other PowerPC platforms are disabled by default.
>
> Historically they have been the most important 32-bit platforms, along
> with PReP.
>
> The problem with making all platforms default to N is that if you take
> the default values for all config options you end up with a config
> that won't build. So we want at least one platform to default to Y,
> and pmac has been as good a choice as any for that (and probably still
> is).
I've got no issue w/grandfathering CHRP or PMAC as default Y. However
I DO NOT think we should default other platforms to 'Y' as that means
updating configs will pick up platforms they dont want.
- k
next prev parent reply other threads:[~2008-10-10 1:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 19:57 [PATCH] powerpc: remove default=y from PMAC and CHRP Kconfigs Timur Tabi
2008-10-08 20:03 ` Benjamin Herrenschmidt
2008-10-08 20:14 ` Timur Tabi
2008-10-08 20:39 ` Benjamin Herrenschmidt
2008-10-08 20:44 ` Timur Tabi
2008-10-09 15:59 ` Matt Sealey
2008-10-09 16:20 ` Timur Tabi
2008-10-09 16:49 ` Matt Sealey
2008-10-09 17:08 ` Scott Wood
2008-10-09 17:23 ` Timur Tabi
2008-10-09 20:18 ` Sven Luther
2008-10-09 21:14 ` Timur Tabi
2008-10-09 21:28 ` Sven Luther
2008-10-09 21:32 ` Timur Tabi
2008-10-10 0:43 ` Paul Mackerras
2008-10-10 1:22 ` Kumar Gala [this message]
2008-10-10 1:51 ` Timur Tabi
2008-10-10 3:01 ` Benjamin Herrenschmidt
2008-10-10 3:01 ` Benjamin Herrenschmidt
2008-10-09 16:21 ` Scott Wood
2008-10-08 20:46 ` Scott Wood
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=68168CE9-D17F-4C55-BF0B-0FAFC3672398@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=timur@freescale.com \
/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).