Messages in this thread | | | Date | Wed, 11 Aug 2004 09:54:59 -0700 | From | William Lee Irwin III <> | Subject | Re: architectures with their own "config PCMCIA" |
| |
On Sat, Aug 07, 2004 at 07:01:22PM +0200, Adrian Bunk wrote: > The following architetures have their own "config PCMCIA" instead of > including drivers/pcmcia/Kconfig (in 2.6.8-rc3-mm1): > - m68k > - s390 > - sparc > - sparc64 > Is there any good reason for this, or would a patch to change these > architectures to include drivers/pcmcia/Kconfig be OK?
I'd like to switch things over to drivers/Kconfig and/or drivers/pcmcia/Kconfig. If the drivers are bust I'll just sweep them when someone complains about the build being bust. One could proactively find these with make allmodconfig and/or allyesconfig, but I suspect that may be too large a set of drivers to digest all at once. Or maybe not -- akpm does scale, after all.
-- wli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |