public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Alex Dubov <oakad@yahoo.com>
Cc: linux-kernel@vger.kernel.org, rmk+lkml@arm.linux.org.uk
Subject: Re: [PATCH 2/2] [MMC] Driver for TI FlashMedia card reader - Kconfig/Makefile entries
Date: Thu, 21 Sep 2006 07:54:56 +0200	[thread overview]
Message-ID: <45122930.10105@drzeus.cx> (raw)
In-Reply-To: <20060921030232.30990.qmail@web36704.mail.mud.yahoo.com>

Alex Dubov wrote:
>
> I kind of fail to follow here. Do you want to switch TIFM_CORE -> MMC_TIFM_SD dependency into
> MMC_TIFM_SD -> TIFM_CORE + TIFM_7XX1 one? It may be slightly more convenient for users (even
> though most are using pre-compiled kernels provided by distribution), but will be logically
> incorrect, doesn't it? And then, what will become of memorystick driver?
>
>   

No no, I want a change from "depends" to "select". That symbolises the
same dependency, but it has slightly different semantics (which it
probably shouldn't, but that's another discussion). With "depends", a
config entry is hidden if its dependencies aren't satisfied. With
"select", it will forcefully enable those dependencies.

>From a user point of view, the former requires knowledge of how all of
these things hangs together (which is expecting a bit much), but the
latter will automatically pull in all the components needed to build the
option the user selects (which is how dependencies should work IMO).

Rgds
Pierre


> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
>   


      reply	other threads:[~2006-09-21  5:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20  6:04 [PATCH 2/2] [MMC] Driver for TI FlashMedia card reader - Kconfig/Makefile entries Alex Dubov
2006-09-20  6:30 ` Pierre Ossman
2006-09-21  3:02   ` Alex Dubov
2006-09-21  5:54     ` Pierre Ossman [this message]

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=45122930.10105@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oakad@yahoo.com \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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