mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Alex Dubov <oakad@yahoo.com>,
	akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] tifm: fix kconfig dependencies
Date: Thu, 14 Oct 2010 05:35:51 +0100	[thread overview]
Message-ID: <20101014043551.GA4760@void.printf.net> (raw)
In-Reply-To: <20101013180729.766f2b3b.randy.dunlap@oracle.com>

Hi,

On Wed, Oct 13, 2010 at 06:07:29PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Fix kconfig dependency warning to satisfy dependencies:
> 
> warning: (MMC_TIFM_SD && MMC && EXPERIMENTAL && PCI || MEMSTICK_TIFM_MS && MEMSTICK && EXPERIMENTAL && PCI) selects TIFM_CORE which has unmet direct dependencies (MISC_DEVICES && EXPERIMENTAL && PCI)
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>  drivers/memstick/host/Kconfig |    1 +
>  drivers/mmc/host/Kconfig      |    1 +
>  2 files changed, 2 insertions(+)
> 
> --- linux-next-20101013.orig/drivers/memstick/host/Kconfig
> +++ linux-next-20101013/drivers/memstick/host/Kconfig
> @@ -7,6 +7,7 @@ comment "MemoryStick Host Controller Dri
>  config MEMSTICK_TIFM_MS
>  	tristate "TI Flash Media MemoryStick Interface support  (EXPERIMENTAL)"
>  	depends on EXPERIMENTAL && PCI
> +	select MISC_DEVICES
>  	select TIFM_CORE
>  	help
>  	  Say Y here if you want to be able to access MemoryStick cards with
> --- linux-next-20101013.orig/drivers/mmc/host/Kconfig
> +++ linux-next-20101013/drivers/mmc/host/Kconfig
> @@ -277,6 +277,7 @@ config MMC_MXC
>  config MMC_TIFM_SD
>  	tristate "TI Flash Media MMC/SD Interface support  (EXPERIMENTAL)"
>  	depends on EXPERIMENTAL && PCI
> +	select MISC_DEVICES
>  	select TIFM_CORE
>  	help
>  	  Say Y here if you want to be able to access MMC/SD cards with

Acked-by: Chris Ball <cjb@laptop.org>
for the mmc hunk.

Andrew, perhaps you should take this to keep the mmc/memstick trees
from modifying files outside of their namespace? (Or we could just
ask Randy to split up the patch; whatever is preferred.)

Thanks,

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

      reply	other threads:[~2010-10-14  4:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  1:07 Randy Dunlap
2010-10-14  4:35 ` Chris Ball [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=20101014043551.GA4760@void.printf.net \
    --to=cjb@laptop.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oakad@yahoo.com \
    --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

Powered by JetHome