Messages in this thread | | | Date | Sat, 7 Aug 2004 19:25:18 +0200 | From | Adrian Bunk <> | Subject | Re: architectures with their own "config PCMCIA" |
| |
On Sat, Aug 07, 2004 at 06:10:51PM +0100, Christoph Hellwig wrote: > 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? > > What about switching them to use drivers/Kconfig instead?
drivers/Kconfig doesn't source drivers/pcmcia/Kconfig (and m68k already uses drivers/Kconfig).
But after a second look, I begin to understand a bit more: Most of the architectures in question even have help text for the PCMCIA option, but the option itself isn't asked.
IOW: It's impossible to enable them.
Is there eny reason for such options that are never visible nor enabled, or could they be removed?
cu Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
- 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/
| |