From: Adrian Bunk <bunk@stusta.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Nick Warne <nick@linicks.net>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org,
"Stefan-W. Hahn" <stefan.hahn@s-hahn.de>,
Willy Tarreau <willy@w.ods.org>
Subject: Re: [2.4 patch] Corrected faulty syntax in drivers/input/Config.in
Date: Sat, 4 Mar 2006 19:56:12 +0100 [thread overview]
Message-ID: <20060304185612.GM9295@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0603041943170.29991@yvahk01.tjqt.qr>
On Sat, Mar 04, 2006 at 07:44:01PM +0100, Jan Engelhardt wrote:
> >> If statement in drivers/input/Config.in for "make xconfig" corrected.
> >>
> >> Signed-off-by: Stefan-W. Hahn <stefan.hahn@s-hahn.de>
> >> Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >>
> >> --- a/drivers/input/Config.in
> >> +++ b/drivers/input/Config.in
> >> @@ -8,7 +8,7 @@ comment 'Input core support'
> >> tristate 'Input core support' CONFIG_INPUT
> >> dep_tristate ' Keyboard support' CONFIG_INPUT_KEYBDEV $CONFIG_INPUT
> >>
> >> -if [ "$CONFIG_INPUT_KEYBDEV" == "n" ]; then
> >> +if [ "$CONFIG_INPUT_KEYBDEV" = "n" ]; then
> >> bool ' Use dummy keyboard driver' CONFIG_DUMMY_KEYB $CONFIG_INPUT
> >> fi
>
> If this is sh compatible code, then == is just as valid -- if xconfig
It is not.
> breaks then, then xconfig is broken, not the file.
Please read at least the section "Introduction" of
Documentation/kbuild/config-language.txt in kernel 2.4
instead of falsely accusing xconfig of being broken.
> Jan Engelhardt
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
prev parent reply other threads:[~2006-03-04 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 18:01 [2.4 patch] Corrected faulty syntax in drivers/input/Config.in Adrian Bunk
2006-03-03 20:26 ` Nick Warne
2006-03-04 18:44 ` Jan Engelhardt
2006-03-04 18:56 ` Adrian Bunk [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=20060304185612.GM9295@stusta.de \
--to=bunk@stusta.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=nick@linicks.net \
--cc=stefan.hahn@s-hahn.de \
--cc=willy@w.ods.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