public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pozsar Balazs <pozsy@sch.bme.hu>
To: Herbert Rosmanith <herp@wildsau.idv-edu.uni-linz.ac.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem in drivers/block/Config.in (PATCH)
Date: Sat, 31 Mar 2001 16:00:27 +0200	[thread overview]
Message-ID: <20010331160027.A26494@balu.sch.bme.hu> (raw)
In-Reply-To: <200103302017.f2UKH8S07176@wildsau.idv-edu.uni-linz.ac.at>
In-Reply-To: <200103302017.f2UKH8S07176@wildsau.idv-edu.uni-linz.ac.at>; from herp@wildsau.idv-edu.uni-linz.ac.at on Fri, Mar 30, 2001 at 10:17:08PM +0200

On Fri, Mar 30, 2001 at 10:17:08PM +0200, Herbert Rosmanith wrote:
> 
> hi,
> 
> I noticed that the option CONFIG_PARIDE_PARPORT will always be "y",
> even if CONFIG_PARIDE_PARPORT="n". I checked with kernels 2.2.18
> and 2.2.19.
> 
> the file responsible is "drivers/block/Config.in", around line 126.
> it reads:
> 
> # PARIDE doesn't need PARPORT, but if PARPORT is configured as a module,
> # PARIDE must also be a module.  The bogus CONFIG_PARIDE_PARPORT option
> # controls the choices given to the user ...
> 
> if [ "$CONFIG_PARPORT" = "y" -o "$CONFIG_PARPORT" = "n" ] ; then
>    define_bool CONFIG_PARIDE_PARPORT y
> else
>    define_bool CONFIG_PARIDE_PARPORT m
> fi
> 
> so, as you can see, CONFIG_PARIDE_PARPORT will be set to "yes" even
> if CONFIG_PARPORT="no".
> 
> why not simply write:
> 
> 	define_bool CONFIG_PARIDE_PARPORT $CONFIG_PARPORT
> 
> instead?

In fact, if we want to get what is said in the comment, we should write:

if [ "$CONFIG_PARPORT" = "m" -a "$CONFIG_PARIDE_PARPORT" = "y" ] ; then
   define_bool CONFIG_PARIDE_PARPORT m
fi

regards,
Balazs Pozsar.

  parent reply	other threads:[~2001-03-31 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-30 20:17 problem in drivers/block/Config.in Herbert Rosmanith
2001-03-30 20:50 ` Tim Waugh
2001-03-31 14:00 ` Pozsar Balazs [this message]
2001-04-01 21:10   ` problem in drivers/block/Config.in (PATCH) Tim Waugh

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=20010331160027.A26494@balu.sch.bme.hu \
    --to=pozsy@sch.bme.hu \
    --cc=herp@wildsau.idv-edu.uni-linz.ac.at \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox