public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: Re: [PATCH] ucb1400_ts depends SND_AC97_BUS
Date: Sat, 9 Dec 2006 21:50:01 -0500	[thread overview]
Message-ID: <200612092150.02940.dtor@insightbb.com> (raw)
In-Reply-To: <20061209003635.e778ff76.randy.dunlap@oracle.com>

On Saturday 09 December 2006 03:36, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> This driver is an AC97 codec according to its help text.
> However, if SOUND is disabled, the "select SND_AC97_BUS"
> still inserts that into the .config file:
> 
> #
> # Sound
> #
> # CONFIG_SOUND is not set
> CONFIG_SND_AC97_BUS=m
> 

I consider this abug in kconfig - users of "select" should not know
full dependency chain for selected symbol.

> Even if the config software followed dependency chains on selects,
> we should try to limit usage of "select" to library-type
> code that is needed (e.g., CRC functions) instead of bus-type
> support.
>

I do not agree here - the way our directory structure is laid out
"sound" comes after "Input device support" menuconfig entry.
Your patch makes user go back and forth in menuconfig, which is
awkward. I think using select is fine when an option depends on
something down the stream. If user already had a chance to select
necessary option then using "depends on" is preferred.

-- 
Dmitry

  reply	other threads:[~2006-12-10  2:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09  8:36 [PATCH] ucb1400_ts depends SND_AC97_BUS Randy Dunlap
2006-12-10  2:50 ` Dmitry Torokhov [this message]
2006-12-10  2:57   ` Randy Dunlap
2006-12-10  3:05     ` Dmitry Torokhov
2006-12-10  3:17       ` Nicolas Pitre
2006-12-10  5:09         ` Randy Dunlap
2006-12-11  3:55           ` Nicolas Pitre
2006-12-11  4:45             ` Randy Dunlap
2008-09-05  2:57             ` Randy Dunlap
2008-09-05  4:37               ` Nicolas Pitre
2008-09-05  4:44                 ` Randy Dunlap
2008-09-05  5:09                   ` Nicolas Pitre
2008-09-05  6:46                     ` Takashi Iwai
2008-09-05 14:52                       ` Nicolas Pitre
2008-09-05 16:26                         ` Takashi Iwai
2008-09-05 16:32                           ` Nicolas Pitre
2008-09-05 17:17                             ` Takashi Iwai
2008-09-05 18:33                               ` Dmitry Torokhov
2008-09-06  9:54                                 ` Takashi Iwai
2008-09-05 21:09                               ` Randy Dunlap
2008-09-06  9:53                                 ` Takashi Iwai
2008-09-05  5:27                   ` Nicolas Pitre

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=200612092150.02940.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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