From: Sam Ravnborg <sam@ravnborg.org>
To: Len Brown <lenb@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Len Brown <len.brown@intel.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
x86@kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [RFC PATCH] x86: create drivers/x86/ from drivers/misc/
Date: Mon, 1 Dec 2008 06:54:06 +0100 [thread overview]
Message-ID: <20081201055406.GB21782@uranus.ravnborg.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0811302338450.3314@localhost.localdomain>
On Mon, Dec 01, 2008 at 12:00:04AM -0500, Len Brown wrote:
> >
> > Any chance we can have this in drivers/Kconfig?
> >
> > Just wrap all of the file in an
> >
> > if X86
> > .....
> > endif
> >
> > So we keep all the drivers/ stuff in one Kconfig file and
> > not spread all over.
>
> grep 'source "drivers"' arch/x86/Kconfig
>
> source "drivers/acpi/Kconfig"
> source "drivers/cpuidle/Kconfig"
> source "drivers/idle/Kconfig"
> source "drivers/pci/pcie/Kconfig"
> source "drivers/pci/Kconfig"
> source "drivers/eisa/Kconfig"
> source "drivers/mca/Kconfig"
> source "drivers/pcmcia/Kconfig"
> source "drivers/pci/hotplug/Kconfig"
> source "drivers/Kconfig"
> source "drivers/firmware/Kconfig"
> source "drivers/x86/Kconfig"
>
> Are the lines above a good example, a bad example,
> or did I miss a nuance of the grand Kconfig design?
Unfortunately a typical example but if you look
closer most of the above is bus stuff, not driver stuff.
This is not the easist part to deal with
as there are > 10 arch to synchronize.
Sam
next prev parent reply other threads:[~2008-12-01 5:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081128213620.2ec593d4.sfr@canb.auug.org.au>
[not found] ` <4930307C.30106@oracle.com>
[not found] ` <20081129083550.3c23af37.sfr@canb.auug.org.au>
[not found] ` <alpine.LFD.2.00.0811281649001.24773@localhost.localdomain>
[not found] ` <alpine.LFD.2.00.0811281702570.24773@localhost.localdomain>
2008-11-28 22:09 ` [RFC PATCH] x86: create drivers/x86/ from drivers/misc/ Len Brown
2008-11-28 22:35 ` Sam Ravnborg
2008-11-28 23:16 ` Len Brown
2008-11-29 0:16 ` Henrique de Moraes Holschuh
2008-12-01 4:35 ` Len Brown
2008-11-29 1:00 ` Randy Dunlap
2008-11-29 7:23 ` Sam Ravnborg
2008-11-29 7:38 ` Sam Ravnborg
2008-12-01 5:00 ` Len Brown
2008-12-01 5:54 ` Sam Ravnborg [this message]
2008-12-01 6:02 ` [RFC PATCH v2] create drivers/platform/x86/ " Len Brown
2008-12-01 6:03 ` [PATCH 1/2] drivers/misc/Makefile, Kconfig: cleanup Len Brown
2008-12-01 7:41 ` Sam Ravnborg
2008-12-01 19:23 ` Len Brown
2008-12-01 6:05 ` [PATCH 2/2] create drivers/platform/x86/ from drivers/misc/ Len Brown
2008-12-01 7:48 ` [RFC PATCH v2] " Ingo Molnar
2008-12-01 19:12 ` Len Brown
2008-11-28 23:20 ` [RFC PATCH] x86: create drivers/x86/ " Len Brown
2008-12-01 4:49 ` Randy Dunlap
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=20081201055406.GB21782@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox