From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Andi Kleen <ak@suse.de>,
linux-arch@vger.kernel.org,
Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Subject: Re: [patch] s390 kconfig cleanup.
Date: Tue, 16 May 2006 10:08:28 +0200 [thread overview]
Message-ID: <1147766908.5289.4.camel@localhost> (raw)
In-Reply-To: <20060515212431.GA25010@moss.sous-sol.org>
On Mon, 2006-05-15 at 14:24 -0700, Chris Wright wrote:
> * Andi Kleen (ak@suse.de) wrote:
> > > That is where the arch people get involved. Can we come
> > > up with a method how to "tag" all menus in the Kconfig files
> > > under drivers/ with a positive list of the architectures
> > > that actually want to include the menu/driver? Or even
> > > better tag the menu/driver with the bus that is required
> > > to attach the device?
> >
> > Xen has a similar problem. They currently have tons of ugly negative
> > checks too. REAL_HARDWARE or similar is needed there, but it might
> > not fit the s390.
> >
> > Checking PCI is a good start and should apply to most menus already.
>
> I like the idea of extending this to the bus like PCI already does.
> Do you have some examples where this doesn't work well?
For example Memory Technology Device (MTD) support, Parallel port
support, Plug and Play support, ATA/ATAPI/MFM/RLL support, ISDN
subsystem, Telephony Support, etc...
Search for all menus tagged with !S390 in the patch and you will get a
good overview.
--
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-05-16 8:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 17:16 [patch] s390 kconfig cleanup Martin Schwidefsky
2006-05-15 17:30 ` Andi Kleen
2006-05-15 19:00 ` Geert Uytterhoeven
2006-05-15 21:24 ` Chris Wright
2006-05-16 8:08 ` Martin Schwidefsky [this message]
2006-05-16 21:12 ` Chris Wright
2006-05-17 8:17 ` Martin Schwidefsky
2006-05-17 11:18 ` Geert Uytterhoeven
2006-05-17 11:22 ` Martin Schwidefsky
2006-05-17 11:24 ` Geert Uytterhoeven
2006-05-17 12:07 ` Martin Schwidefsky
2006-05-17 12:12 ` Geert Uytterhoeven
2006-05-17 12:24 ` Martin Schwidefsky
2006-05-17 13:25 ` Matthew Wilcox
2006-05-17 16:50 ` Martin Schwidefsky
2006-05-17 20:06 ` Geert Uytterhoeven
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=1147766908.5289.4.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=ak@suse.de \
--cc=chrisw@sous-sol.org \
--cc=linux-arch@vger.kernel.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 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.