public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: Andrea Barisani <lcars@infis.univ.trieste.it>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: kernel 2.6.0, wrong Kconfig directives
Date: Fri, 26 Dec 2003 06:25:20 +0900	[thread overview]
Message-ID: <871xqsbnen.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20031225203853.GV31789@actcom.co.il>

Muli Ben-Yehuda <mulix@mulix.org> writes:

> > I see. So why did we need the SOUND_GAMEPORT?
> 
> I thought I explained this above, quite verbosely :-) 
> Rather than make the sound drivers depend directly on GAMEPORT, which
> is troublesome because Kconfig has no provisions for this type of
> dependancy, we create an artificial dependency, SOUND_GAMEPORT, which
> the sound driver depends on. SOUND_GAMEPORT depends on GAMEPORT, and
> Kconfig ends up doing the right thing. I hope that was clearer. 

Umm... SOUND_GAMEPORT is always true, so GAMEPORT is just option, not
dependency.

It may be good to be documented as the help of Kconfig instead of
SOUND_GAMEPORT...
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2003-12-25 21:25 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 [this message]
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=871xqsbnen.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=akpm@osdl.org \
    --cc=lcars@infis.univ.trieste.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.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