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-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
