All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Arnd Bergmann <arnd@arndb.de>, zippel@linux-m68k.org
Cc: Christoph Hellwig <hch@infradead.org>,
	wli@holomorphy.com, davem@redhat.com, geert@linux-m68k.org,
	schwidefsky@de.ibm.com, linux390@de.ibm.com,
	sparclinux@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: architectures with their own "config PCMCIA"
Date: Wed, 11 Aug 2004 20:17:25 +0000	[thread overview]
Message-ID: <20040811201725.GJ26174@fs.tum.de> (raw)
In-Reply-To: <200408072013.01168.arnd@arndb.de>

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


WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@fs.tum.de>
To: Arnd Bergmann <arnd@arndb.de>, zippel@linux-m68k.org
Cc: Christoph Hellwig <hch@infradead.org>,
	wli@holomorphy.com, davem@redhat.com, geert@linux-m68k.org,
	schwidefsky@de.ibm.com, linux390@de.ibm.com,
	sparclinux@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: architectures with their own "config PCMCIA"
Date: Wed, 11 Aug 2004 22:17:25 +0200	[thread overview]
Message-ID: <20040811201725.GJ26174@fs.tum.de> (raw)
In-Reply-To: <200408072013.01168.arnd@arndb.de>

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


  parent reply	other threads:[~2004-08-11 20:17 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-07 17:01 architectures with their own "config PCMCIA" Adrian Bunk
2004-08-07 17:01 ` Adrian Bunk
2004-08-07 17:10 ` Christoph Hellwig
2004-08-07 17:10   ` Christoph Hellwig
2004-08-07 17:25   ` Adrian Bunk
2004-08-07 17:25     ` Adrian Bunk
2004-08-07 18:12     ` Arnd Bergmann
2004-08-07 18:12       ` Arnd Bergmann
2004-08-07 20:36       ` Geert Uytterhoeven
2004-08-07 20:36         ` Geert Uytterhoeven
2004-08-07 21:41         ` Arnd Bergmann
2004-08-07 21:41           ` Arnd Bergmann
2004-08-11 16:45           ` Christoph Hellwig
2004-08-11 16:45             ` Christoph Hellwig
2004-08-11 20:17       ` Adrian Bunk [this message]
2004-08-11 20:17         ` Adrian Bunk
2004-08-11 21:40         ` Sam Ravnborg
2004-08-11 21:40           ` Sam Ravnborg
2004-08-12  0:10           ` Adrian Bunk
2004-08-12  0:10             ` Adrian Bunk
2004-08-12  8:59             ` Roman Zippel
2004-08-12  8:59               ` Roman Zippel
2004-08-14 20:47               ` Adrian Bunk
2004-08-14 20:47                 ` Adrian Bunk
2004-08-15 17:32                 ` Roman Zippel
2004-08-15 17:32                   ` Roman Zippel
2004-08-15 19:37                   ` Geert Uytterhoeven
2004-08-15 19:37                     ` Geert Uytterhoeven
2004-08-15 20:15                     ` Adrian Bunk
2004-08-15 20:15                       ` Adrian Bunk
2004-08-15 23:01                     ` Roman Zippel
2004-08-15 23:01                       ` Roman Zippel
2004-08-15 23:22                       ` Adrian Bunk
2004-08-15 23:22                         ` Adrian Bunk
2004-08-11 21:45         ` Roman Zippel
2004-08-11 21:45           ` Roman Zippel
2004-08-12  0:18           ` Adrian Bunk
2004-08-12  0:18             ` Adrian Bunk
2004-08-12  2:19             ` Randy.Dunlap
2004-08-12  2:19               ` Randy.Dunlap
2004-08-11 16:54 ` William Lee Irwin III
2004-08-11 16:54   ` William Lee Irwin III

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040811201725.GJ26174@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=arnd@arndb.de \
    --cc=davem@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=hch@infradead.org \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux390@de.ibm.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=wli@holomorphy.com \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.