From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Andi Kleen <ak@suse.de>
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:28:06 +0200 [thread overview]
Message-ID: <1151674086.11575.24.camel@localhost> (raw)
In-Reply-To: <200606301509.16981.ak@suse.de>
On Fri, 2006-06-30 at 15:09 +0200, Andi Kleen wrote:
> > > 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.
None of them seems appropriate. The things the patch deactives for s390
are vastly different (ATA/IDE, Parallel port, Plug and Play, I2C, I2O
and so on). You will end up adding a lot of new config options.
> What stops users from plugging a PCI sound card into your PCI slots
> BTW?
Which PCI slot? s390 doesn't have PCI slots.
> 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 ...)
I don't mind doing it but the question still is how.
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2006-06-30 13:28 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
2006-06-30 13:20 ` Geert Uytterhoeven
2006-06-30 13:28 ` Martin Schwidefsky [this message]
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=1151674086.11575.24.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=matthew@wil.cx \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.