public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Adrian Bunk <bunk@stusta.de>, Paul Mackerras <paulus@samba.org>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] arch/powerpc/Kconfig: fix the EMBEDDED6xx dependencies
Date: Sun, 29 Jul 2007 21:31:37 +0200	[thread overview]
Message-ID: <200707292131.38348.arnd@arndb.de> (raw)
In-Reply-To: <20070728152704.GA30976@stusta.de>

On Saturday 28 July 2007, Adrian Bunk wrote:
> On Mon, Dec 04, 2006 at 02:06:34PM +1100, Paul Mackerras wrote:
> > Adrian Bunk writes:
> > 
> > > This patch changes the EMBEDDED6xx dependencies to the equivalent 
> > > dependency that seems to have been intended.
> > 
> > Nack - CONFIG_EMBEDDED6xx is going away entirely, soon.
> 
> Still there - and still with this strange dependency.

The last time I sent my patch to clean up CONFIG_EMBEDDED6xx and a few
other Kconfig options I still left it intact, but it becomes unnecessary
after that.

I still think that having high-level options like

* embedded6xx
  * MPC7448HPC2
  * holly
  * linkstation
* PPC_83xx
  * MPC8313_RDB
  * MPC832x_MDS
  * MPC832x_RDB

helps keep the platform selection more structured and readable, but the
dependency on !SMP should probably go into the individual platforms that
are actually broken, if any, not into the high-level option.

	Arnd <><

  reply	other threads:[~2007-07-29 21:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01 11:54 [2.6 patch] arch/powerpc/Kconfig: fix the EMBEDDED6xx dependencies Adrian Bunk
2006-12-04  3:06 ` Paul Mackerras
2007-07-28 15:27   ` Adrian Bunk
2007-07-29 19:31     ` Arnd Bergmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-22  4:17 Adrian Bunk

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=200707292131.38348.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --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