From: Kumar Gala <galak@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
arnd@arndb.de, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [patch 00/13] CPU selection Kconfig cleanup, take 3
Date: Sat, 16 Jun 2007 18:47:56 -0500 [thread overview]
Message-ID: <AB18F3F9-C844-4ECE-8EE3-7B05DDD5669E@kernel.crashing.org> (raw)
In-Reply-To: <1181954800.26853.103.camel@localhost.localdomain>
On Jun 15, 2007, at 7:46 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2007-06-14 at 08:33 -0500, Kumar Gala wrote:
>> On Jun 13, 2007, at 8:46 PM, Paul Mackerras wrote:
>>
>>> Most of this series of patches touch 8xxx or 5xxx stuff in one
>>> way or
>>> another, so I'll leave it to Kumar to make the decision about them.
>>> I'll put in 1/13.
>>
>> Arnd,
>>
>> I'm a little hesitant to move the embedded ppc's over to
>> multiplatform quite yet. One feature I wanted was in Kconfig a way
>> to enforce the selection of at least one choice, as well as being
>> able to optimize things since we only had one choice selected.
>>
>> See the following thread for discussion I had with Sam & Roman on the
>> subject:
>>
>> http://marc.info/?t=117156757000002&r=1&w=2
>
> I missed that discussion... but without actually reading it (yet),
> I can
> already tell that I don't like the way you propose it. I would much
> prefer the CONFIG_xxx_ONLY_ONE be -generated- by the multiple choice
> menu if only one choice has been selected.
>
> That could be an optional argument to the menu stuff to set that.
That was my intent, that the Kconfig system would help in telling us
only one choice was selected and we could optimize based on that. In
addition, to ensure that at least one choice was selected. I believe
Rob Landley came across an issue that exists today with MULTIPLATFORM
support in that we can attempt to build a kernel w/o any system.
http://marc.info/?t=117529164800005&r=1&w=2
- k
next prev parent reply other threads:[~2007-06-16 23:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 16:30 [patch 00/13] CPU selection Kconfig cleanup, take 3 arnd
2007-06-12 16:30 ` [patch 01/13] powerpc: split out CPU specific options into a new Kconfig file arnd
2007-06-12 16:30 ` [patch 02/13] powerpc: move 82xx/83xx/86xx Kconfig options to platform selection arnd
2007-06-12 16:30 ` [patch 03/13] powerpc: rename add_bridge to avoid namespace clashes arnd
2007-06-12 16:30 ` [patch 04/13] powerpc: multiplatformize 8{2,3,6}xx configuration arnd
2007-06-12 16:30 ` [patch 05/13] powerpc: multiplatformize embedded6xx configuration arnd
2007-06-12 16:30 ` [patch 06/13] powerpc: multiplatformize 52xx configuration arnd
2007-06-12 16:30 ` [patch 07/13] powerpc: multiplatformize 85xx configuration arnd
2007-06-12 16:30 ` [patch 08/13] powerpc: autoselect PPC_MULTIPLATFORM arnd
2007-06-12 16:30 ` [patch 09/13] powerpc: autoselect optimal -mcpu= flag by platform arnd
2007-06-12 16:30 ` [patch 10/13] powerpc: mpc82xx_ads build fix arnd
2007-06-12 16:30 ` [patch 11/13] powerpc: killl isa_{io,mem}_base definitions for !PCI arnd
2007-06-12 16:30 ` [patch 12/13] powerpc: fix building without PCI arnd
2007-06-14 1:44 ` Paul Mackerras
2007-06-14 7:58 ` Arnd Bergmann
2007-06-12 16:30 ` [patch 13/13] disallow building powermac and tsi108 " arnd
2007-06-14 1:46 ` [patch 00/13] CPU selection Kconfig cleanup, take 3 Paul Mackerras
2007-06-14 13:33 ` Kumar Gala
2007-06-14 23:51 ` Arnd Bergmann
2007-06-16 23:52 ` Kumar Gala
2007-06-17 0:14 ` Arnd Bergmann
2007-06-17 0:22 ` Segher Boessenkool
2007-06-17 14:46 ` Kumar Gala
2007-06-17 23:09 ` Arnd Bergmann
2007-06-18 4:32 ` Kumar Gala
2007-06-19 0:05 ` Kumar Gala
2007-06-15 18:28 ` Kim Phillips
2007-06-16 23:48 ` Kumar Gala
2007-06-16 0:46 ` Benjamin Herrenschmidt
2007-06-16 23:47 ` Kumar Gala [this message]
2007-06-17 0:19 ` Segher Boessenkool
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=AB18F3F9-C844-4ECE-8EE3-7B05DDD5669E@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sam@ravnborg.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).