linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nick Warne" <nick@linicks.net>
To: "Adrian Bunk" <bunk@stusta.de>
Cc: "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: Fri, 3 Mar 2006 20:26:33 +0000	[thread overview]
Message-ID: <7c3341450603031226o55f6c77ah@mail.gmail.com> (raw)
In-Reply-To: <20060303180100.GV9295@stusta.de>

> 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>
>
> ---
>
> This patch was sent by Stefan-W. Hahn on:
> - 26 Feb 2006
>
> --- 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

This was my patch, and after I saw that a bit later (Duh!), I did ask:

http://marc.theaimsgroup.com/?l=linux-kernel&m=112966037407189&w=2

But got no feedback, and it was accepted, so I presumed all was OK.

So it looks like breaks in xconfig, and not menuconfig (what I use).

Nick

  reply	other threads:[~2006-03-03 20:26 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 [this message]
2006-03-04 18:44   ` Jan Engelhardt
2006-03-04 18:56     ` Adrian Bunk

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=7c3341450603031226o55f6c77ah@mail.gmail.com \
    --to=nick@linicks.net \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --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;
as well as URLs for NNTP newsgroup(s).