From: Tim Waugh <twaugh@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: [patch] Re: paride/Config.in and bool vs. mconfig 0.20
Date: Tue, 4 Dec 2001 11:27:10 +0000 [thread overview]
Message-ID: <20011204112710.X14028@redhat.com> (raw)
In-Reply-To: <20011202172957.A11453@emma1.emma.line.org>
In-Reply-To: <20011202172957.A11453@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Sun, Dec 02, 2001 at 05:29:57PM +0100
On Sun, Dec 02, 2001 at 05:29:57PM +0100, Matthias Andree wrote:
> I tried to configure 2.4.17pre2 with mconfig 0.20, it said:
>
> | drivers/block/paride/Config.in: 32: warning: bool command has extra
> | arguments
>
> And rightly so, bool wants the configuration question and the parameter,
> nothing else.
>
> Either that needs some dep_ stuff or it has indeed an extra argument, I
> cannot decide which one is correct, so I'm not providing a patch now.
That option really is just a bool. Here is the fix.
Tim.
*/
--- linux/drivers/block/paride/Config.in.bool Tue Dec 4 11:23:35 2001
+++ linux/drivers/block/paride/Config.in Tue Dec 4 11:24:17 2001
@@ -29,7 +29,7 @@
dep_tristate ' Shuttle EPAT/EPEZ protocol' CONFIG_PARIDE_EPAT $CONFIG_PARIDE
if [ "$CONFIG_PARIDE_EPAT" != "n" ]; then
if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then
- bool ' Support c7/c8 chips (EXPERIMENTAL)' CONFIG_PARIDE_EPATC8 $CONFIG_PARIDE
+ bool ' Support c7/c8 chips (EXPERIMENTAL)' CONFIG_PARIDE_EPATC8
fi
fi
prev parent reply other threads:[~2001-12-04 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 16:29 paride/Config.in and bool vs. mconfig 0.20 Matthias Andree
2001-12-04 11:27 ` Tim Waugh [this message]
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=20011204112710.X14028@redhat.com \
--to=twaugh@redhat.com \
--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 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.