linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Olof Johansson <olof@lixom.net>, Paul Mackerras <paulus@samba.org>
Subject: Re: RFC: arch/powerpc Kconfig cleanup
Date: Fri, 16 Mar 2007 11:54:49 +0100	[thread overview]
Message-ID: <200703161154.50218.arnd@arndb.de> (raw)
In-Reply-To: <3999EC16-6013-4632-A0A5-376D006CE057@kernel.crashing.org>

On Friday 16 March 2007, Kumar Gala wrote:
> >
> > At some point we should also separate the common code (mostly spufs)
> > from the cell native support that does not apply to ps3 and celleb.
>=20
> Fair point, I'll fix that up. =A0I'm more interested if people are ok =A0
> with having the 'Cell Broadband Engine options' under 'Platform =A0
> support' is ok or if it should stay at the top level.

I was never happy with having it at the top level, but I couldn't
figure out a better way at the time, and I think I just copied what
some other platforms did.

I think it would be good to turn them into menuconfig entries, so
that if platforms/Kconfig basically contains

source arch/powerpc/platforms/pseries/Kconfig
source arch/powerpc/platforms/powermac/Kconfig
source arch/powerpc/platforms/cell/Kconfig
source arch/powerpc/platforms/celleb/Kconfig
source arch/powerpc/platforms/ps3/Kconfig
=2E..

each of them can either be

config CELLEB
	bool "support for celleb"
	select FOO
	select BAR

or

menuconfig PSERIES
	bool "support for pseries"
	select BAR
	select BAZ
config PSERIES_FOO
	bool "option foo for pseries"
	depends on PSERIES
endmenu

	Arnd <><

  reply	other threads:[~2007-03-16 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 23:34 RFC: arch/powerpc Kconfig cleanup Kumar Gala
2007-03-15 23:45 ` Grant Likely
2007-03-16  0:18 ` Olof Johansson
2007-03-16  0:34 ` Arnd Bergmann
2007-03-16  1:16   ` Kumar Gala
2007-03-16 10:54     ` Arnd Bergmann [this message]
2007-03-16  0:43 ` Geoff Levand
2007-03-16  6:59 ` Li Yang-r58472

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=200703161154.50218.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    --cc=paulus@samba.org \
    /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).