[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081201055406.GB21782@uranus.ravnborg.org>
Date: Mon, 1 Dec 2008 06:54:06 +0100
From: Sam Ravnborg <sam@...nborg.org>
To: Len Brown <lenb@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Len Brown <len.brown@...el.com>, linux-next@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Randy Dunlap <randy.dunlap@...cle.com>, x86@...nel.org,
linux-acpi@...r.kernel.org
Subject: Re: [RFC PATCH] x86: create drivers/x86/ from drivers/misc/
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists