Messages in this thread | | | Date | Wed, 11 Aug 2004 22:17:25 +0200 | From | Adrian Bunk <> | Subject | Re: architectures with their own "config PCMCIA" |
| |
On Sat, Aug 07, 2004 at 08:12:56PM +0200, Arnd Bergmann wrote: >... > On Samstag, 7. August 2004 19:25, Adrian Bunk wrote: > > Is there eny reason for such options that are never visible nor enabled, > > or could they be removed? > > Yes, the reason is that some other options depend on them. We added the > PCMCIA option to arch/s390/Kconfig to stop kbuild from asking about > some drivers that won't work anyway. > > E.g. drivers/scsi/pcmcia starts with > > menu "PCMCIA SCSI adapter support" > depends on SCSI!=n && PCMCIA!=n && MODULES > > which evaluate to true if the PCMCIA option is not known. Changing > that to > > menu "PCMCIA SCSI adapter support" > depends on SCSI && PCMCIA && MODULES > > solves this in a different way, but I'm not 100% sure if it still has > the same meaning.
Roman, is it intentional that PCMCIA!=n is true if there's no PCMCIA option, or is it simply a bug?
> Arnd <><
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/
| |