All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ron Murray <rjmx@rjmx.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] CS461x gameport code isn't being included in build
Date: Sat, 04 Dec 2004 17:18:46 -0500	[thread overview]
Message-ID: <41B237C6.9030404@rjmx.net> (raw)

    I've found a typo in drivers/input/gameport/Makefile in kernel
2.6.9 which effectively prevents the CS461x gameport code from
being included. Here's the diff:

--- linux-2.6.9/drivers/input/gameport/Makefile.orig	2004-10-18 
17:53:06.000000000 -0400
+++ linux-2.6.9/drivers/input/gameport/Makefile	2004-12-04 
16:51:12.000000000 -0500
@@ -5,7 +5,7 @@
  # Each configuration option enables a list of files.

  obj-$(CONFIG_GAMEPORT)		+= gameport.o
-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



    Note: the change is to a lower-case 'x' in
'CONFIG_GAMEPORT_CS461x'. It's hard to see.

    Kconfig in the same directory has


 >> config GAMEPORT_CS461x
 >> 	tristate "Crystal SoundFusion gameport support"
 >> 	depends on GAMEPORT


    This patch brings the Makefile into line with the spelling in
Kconfig.

Signed-off-by: Ron Murray <rjmx@rjmx.net>

  .....Ron

-- 
Ron Murray   (rjmx@rjmx.net)
http://www.rjmx.net/~ron
GPG Public Key Fingerprint: F2C1 FC47 5EF7 0317 133C  D66B 8ADA A3C4 
D86C 74DE

             reply	other threads:[~2004-12-04 22:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04 22:18 Ron Murray [this message]
2004-12-05 12:53 ` [PATCH] CS461x gameport code isn't being included in build Cal Peake
2004-12-08 12:51 ` Adrian Bunk
     [not found] <200501040609.j0469qtl004738@hera.kernel.org>
2005-01-06 12:41 ` Alan Cox

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=41B237C6.9030404@rjmx.net \
    --to=rjmx@rjmx.net \
    --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.