From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: torvalds@osdl.org
Subject: Re: [PATCH] CS461x gameport code isn't being included in build
Date: Thu, 06 Jan 2005 12:41:34 +0000 [thread overview]
Message-ID: <1104940156.24187.186.camel@localhost.localdomain> (raw)
In-Reply-To: <200501040609.j0469qtl004738@hera.kernel.org>
On Maw, 2005-01-04 at 04:14, Linus Torvalds applied:
> -obj-$(CONFIG_GAMEPORT_CS461X) += cs461x.o
> +obj-$(CONFIG_GAMEPORT_CS461x) += cs461x.o
> obj-$(CONFIG_GAMEPORT_EMU10K1) += emu10k1-gp.o
> obj-$(CONFIG_GAMEPORT_FM801) += fm801-gp.o
> obj-$(CONFIG_GAMEPORT_L4) += lightning.o
This change makes the CS461x unique in having lower case in the config
name. In the previous discussion on the kernel list this patch was
rejected and instead the 461x was changed to 461X in the Kconfig file
keeping consistency with the rest of the kernel.
Alan
next parent reply other threads:[~2005-01-06 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501040609.j0469qtl004738@hera.kernel.org>
2005-01-06 12:41 ` Alan Cox [this message]
2004-12-04 22:18 [PATCH] CS461x gameport code isn't being included in build Ron Murray
2004-12-05 12:53 ` Cal Peake
2004-12-08 12:51 ` 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=1104940156.24187.186.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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