From: Andi Kleen <ak@suse.de>
To: schwidefsky@de.ibm.com
Cc: linux-arch@vger.kernel.org, geert@linux-m68k.org,
Keir.Fraser@cl.cam.ac.uk, chrisw@sous-sol.org, matthew@wil.cx,
akpm@osdl.org
Subject: Re: [patch] s390 kconfig cleanup, 2nd version.
Date: Fri, 30 Jun 2006 15:09:16 +0200 [thread overview]
Message-ID: <200606301509.16981.ak@suse.de> (raw)
In-Reply-To: <1151672682.11575.16.camel@localhost>
On Friday 30 June 2006 15:04, Martin Schwidefsky wrote:
> On Fri, 2006-06-30 at 14:44 +0200, Andi Kleen wrote:
> > On Friday 30 June 2006 14:26, Martin Schwidefsky wrote:
> > > Hi folks,
> > > it has been a few weeks since the s390 kconfig discussion died down.
> > > I have put together a new patch that includes all of the suggestions
> > > made so far. With this patch "make allyesconfig" and "make allmodconfig"
> > > now works on s390.
> > >
> > > Please check that it does not break anything on your favorite
> > > architecture. It really shouldn't but you never know. I want to push
> > > this patch soon.
> >
> > I must say I still hate the negative !S390. It would be much better
> > to define something positive. If PCI doesn't work maybe something
> > else.
>
> Well, I don't like these negative !S390 depends as well. But I can't
> help it, there is no other existing config symbol that can be used for a
> positive dependency. Hardware that is built into the machine and is not
> attached via some kind of bus does not have any dependency.
But one can be invented.
DESKTOP_HARDWARE
SMALL_IRON
END_USER_PCI
...
Chose one.
What stops users from plugging a PCI sound card into your PCI slots
BTW?
Initially it can be set dependent on !S390 and then later migrated
into all the architectures (you can probably recruit someone on l-k
to do it if you don't want to do it yourself ...)
-Andi
next prev parent reply other threads:[~2006-06-30 13:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 12:26 [patch] s390 kconfig cleanup, 2nd version Martin Schwidefsky
2006-06-30 12:39 ` Geert Uytterhoeven
2006-06-30 12:54 ` Martin Schwidefsky
2006-06-30 12:44 ` Andi Kleen
2006-06-30 13:04 ` Martin Schwidefsky
2006-06-30 13:09 ` Andi Kleen [this message]
2006-06-30 13:20 ` Geert Uytterhoeven
2006-06-30 13:28 ` Martin Schwidefsky
2006-06-30 14:05 ` Andi Kleen
2006-06-30 14:15 ` Geert Uytterhoeven
2006-06-30 14:20 ` Martin Schwidefsky
2006-07-03 23:15 ` Arnd Bergmann
2006-07-03 23:35 ` Matthew Wilcox
2006-07-04 12:42 ` Arnd Bergmann
2006-07-04 13:08 ` Geert Uytterhoeven
2006-07-04 15:23 ` Arnd Bergmann
2006-07-04 18:09 ` Matthew Wilcox
2006-07-01 2:38 ` Paul Mackerras
2006-06-30 14:13 ` Kyle McMartin
2006-06-30 14:20 ` Andi Kleen
2006-06-30 17:41 ` Andrew Morton
2006-06-30 18:28 ` Andi Kleen
2006-07-03 9:10 ` Martin Schwidefsky
2006-07-03 9:20 ` Andrew Morton
2006-07-03 10:35 ` Martin Schwidefsky
2006-07-07 16:19 ` [Kconfig] add disable command (was Re: [patch] s390 kconfig cleanup, 2nd version) Martin Schwidefsky
2006-07-07 19:27 ` Andrew Morton
2006-07-07 16:19 ` [Kconfig] use " Martin Schwidefsky
2006-07-07 19:48 ` Matthew Wilcox
2006-07-08 23:42 ` Ralf Baechle
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=200606301509.16981.ak@suse.de \
--to=ak@suse.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=schwidefsky@de.ibm.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