public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Guennadi Liakhovetski <gl@dsa-ac.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_SOUND_GAMEPORT in 2.5
Date: Thu, 14 Mar 2002 09:19:15 +0100	[thread overview]
Message-ID: <20020314091915.C31998@ucw.cz> (raw)
In-Reply-To: <20020313182054.A31062@ucw.cz> <Pine.LNX.4.33.0203140910150.15512-100000@pcgl.dsa-ac.de>
In-Reply-To: <Pine.LNX.4.33.0203140910150.15512-100000@pcgl.dsa-ac.de>; from gl@dsa-ac.de on Thu, Mar 14, 2002 at 09:12:04AM +0100

On Thu, Mar 14, 2002 at 09:12:04AM +0100, Guennadi Liakhovetski wrote:
> > > drivers/input/gameport/Config.in doesn't seem quite right to me, in
> > > general and for ARM specifically:
> > > if [ "$CONFIG_GAMEPORT" = "m" ]; then
> > > 	define_tristate CONFIG_SOUND_GAMEPORT m
> > > fi
> > > if [ "$CONFIG_GAMEPORT" != "m" ]; then
> > > 	define_tristate CONFIG_SOUND_GAMEPORT y
> > > fi
> > >
> > > Could the maintainer please change this?
> >
> > What's the problem here?
> 
> The problem is, that if you don't have anything like a sound-card/gameport
> at all, CONFIG_SOUND_GAMEPORT still will be YES. Ok, I didn't check in the
> code, maybe it doesn't add a single byte to the kernel, .config looks a
> bit confusing, doesn't it?

Yes, it doesn't add anything. It's just a switch that *disables*
gameport code in sound drivers if no gameport support is selected in the
kernel.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-03-14  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 15:27 CONFIG_SOUND_GAMEPORT in 2.5 Guennadi Liakhovetski
2002-03-13 17:20 ` Vojtech Pavlik
2002-03-14  8:12   ` Guennadi Liakhovetski
2002-03-14  8:19     ` Vojtech Pavlik [this message]
2002-03-14  9:07       ` Guennadi Liakhovetski
2002-03-14  9:12         ` Vojtech Pavlik

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=20020314091915.C31998@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=gl@dsa-ac.de \
    --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