public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <mulix@mulix.org>
To: Andrea Barisani <lcars@infis.univ.trieste.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.0, wrong Kconfig directives
Date: Thu, 25 Dec 2003 21:39:49 +0200	[thread overview]
Message-ID: <20031225193948.GP31789@actcom.co.il> (raw)
In-Reply-To: <20031222235622.GA17030@sole.infis.univ.trieste.it>

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

On Tue, Dec 23, 2003 at 12:56:23AM +0100, Andrea Barisani 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.

line 24 is correct. CONFIG_SOUND_GAMEPORT is an odd beast, see
e.g.
http://marc.theaimsgroup.com/?l=linux-kernel&m=106479206731633&w=2 for
details. Please leave poor CONFIG_GAMEPORT alone. 

Cheers, 
Muli 
-- 
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 --]

  parent reply	other threads:[~2003-12-25 19:39 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
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 [this message]
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=20031225193948.GP31789@actcom.co.il \
    --to=mulix@mulix.org \
    --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