public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <mulix@mulix.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Andrea Barisani <lcars@infis.univ.trieste.it>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	alsa-devel@alsa-project.org
Subject: Re: kernel 2.6.0, wrong Kconfig directives
Date: Thu, 25 Dec 2003 21:51:16 +0200	[thread overview]
Message-ID: <20031225195115.GQ31789@actcom.co.il> (raw)
In-Reply-To: <87smj8bt6y.fsf@devron.myhome.or.jp>

[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]

On Fri, Dec 26, 2003 at 04:20:21AM +0900, OGAWA Hirofumi wrote:
> 
> > - SOUND_GAMEPORT option is always turned on
> > 
> > ./drivers/input/gameport/Kconfig
> > 
> > 22: config SOUND_GAMEPORT
> > 23:         tristate
> > 24:         default y if GAMEPORT!=m
> > 25:         default m if GAMEPORT=m
> > 
> > line 24 is definetly wrong, option is enabled if GAMEPORT=n.
> 
> This patch uses "select" for the dependency of GAMEPORT.

This is wrong. It forces the joystick (GAMEPORT) in even when it's not
needed, whereas SOUND_GAMEPORT handles all cases fine. That way lies
kernel bloat. Please apply this documentation patch instead: 

Index: drivers/input/gameport/Kconfig
===================================================================
RCS file: /home/muli/kernel/cvsroot/linux-2.5/drivers/input/gameport/Kconfig,v
retrieving revision 1.4
diff -u -u -r1.4 Kconfig
--- drivers/input/gameport/Kconfig	26 Sep 2003 00:23:18 -0000	1.4
+++ drivers/input/gameport/Kconfig	25 Dec 2003 19:48:49 -0000
@@ -19,6 +19,17 @@
 	  To compile this driver as a module, choose M here: the
 	  module will be called gameport.
 
+
+# Yes, this looks a bit odd. Yes, it ends up being turned on in lots
+# of cases. Please don't touch it. It is here to handle the case where
+# a sound driver can be either a module or compiled in if GAMEPORT is
+# not selected, but must be a module if the joystick is selected as a 
+# module. The sound driver calls GAMEPORT functions. If GAMEPORT is
+# not selected, stubs are provided. If GAMEPORT is built in,
+# everything is fine. If GAMEPORT is a module, however, it would need
+# to be loaded for the sound driver to be able to link
+# properly. Therefore, the sound driver must be a module as well in
+# that case (and the GAMEPORT module must be loaded first). 
 config SOUND_GAMEPORT
 	tristate
 	default y if GAMEPORT!=m
-- 
Muli Ben-Yehuda
http://www.mulix.org | http://mulix.livejournal.com/

"the nucleus of linux oscillates my world" - gccbot@#offtopic


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-12-25 19:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-22 23:56 kernel 2.6.0, wrong Kconfig directives Andrea Barisani
2003-12-25 19:20 ` OGAWA Hirofumi
2003-12-25 19:51   ` Muli Ben-Yehuda [this message]
2003-12-25 20:33     ` OGAWA Hirofumi
2003-12-25 20:38       ` Muli Ben-Yehuda
2003-12-25 21:25         ` OGAWA Hirofumi
2003-12-26  1:23           ` OGAWA Hirofumi
2003-12-25 19:39 ` Muli Ben-Yehuda
2004-01-05 22:17 ` Adrian Bunk
2004-01-05 22:59   ` Andrea Barisani
2004-01-06  1:22     ` 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=20031225195115.GQ31789@actcom.co.il \
    --to=mulix@mulix.org \
    --cc=akpm@osdl.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=lcars@infis.univ.trieste.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox