From: Vojtech Pavlik <vojtech@suse.cz>
To: Brad Hards <bhards@bigpond.net.au>
Cc: James Simmons <jsimmons@transvirtual.com>,
torvalds@transmeta.com,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
vojtech@twilight.ucw.cz
Subject: Re: [patch] Typo fixes in input code
Date: Mon, 8 Jul 2002 13:08:16 +0200 [thread overview]
Message-ID: <20020708130816.C22144@ucw.cz> (raw)
In-Reply-To: <200207071222.48783.bhards@bigpond.net.au>; from bhards@bigpond.net.au on Sun, Jul 07, 2002 at 12:22:48PM +1000
On Sun, Jul 07, 2002 at 12:22:48PM +1000, Brad Hards wrote:
> On Sun, 7 Jul 2002 03:48, James Simmons wrote:
> > You patch is right except for drivers/input/gameport/Config.help. That was
> > right before your patch.
> OK. I assumed that Config.in was the authoritative source, and Config.help
> should match. Looks like (based on the Makefile) that I probably should have
> changed it to be CONFIG_GAMEPORT_EMU10K1 in the Config.in. In fact, that
> driver won't ever be built with vanilla 2.5.25, with or without the previous
> patch
>
> BK already has the previous change applied, so this in an incremental diff:
>
> <bk text>
> EMU10K1 build fix
>
> Revert the CONFIG_INPUT_EMU10K1 change to drivers/input/gameport/Config.help,
> and change drivers/input/gameport/Config.in to use CONFIG_GAMEPORT_EMU10K1
> </bk text>
Thanks, applied.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-07-08 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 23:54 linux 2.5.25 Linus Torvalds
2002-07-06 5:35 ` Albert D. Cahalan
2002-07-06 8:17 ` [patch] Typo fixes in input code Brad Hards
2002-07-06 17:48 ` James Simmons
2002-07-07 2:22 ` Brad Hards
2002-07-08 11:08 ` Vojtech Pavlik [this message]
2002-07-06 13:54 ` linux 2.5.25 (and LVM) Matthias Andree
2002-07-08 8:43 ` Joe Thornber
2002-07-08 8:40 ` Alexander Viro
2002-07-08 1:04 ` linux 2.5.25 Tim Pepper
2002-07-08 12:44 ` [PATCH] 2.5.25 end_request trivia Martin Dalecki
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=20020708130816.C22144@ucw.cz \
--to=vojtech@suse.cz \
--cc=bhards@bigpond.net.au \
--cc=jsimmons@transvirtual.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=vojtech@twilight.ucw.cz \
/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
all inboxes | Powered by JetHome®