linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>,
	Graeme Gregory <gg@slimlogic.co.uk>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: TPS65910 depends on I2C and must be built in
Date: Wed, 11 May 2011 14:35:18 +0100	[thread overview]
Message-ID: <1305120918.3277.16.camel@odin> (raw)
In-Reply-To: <1305103667-17454-1-git-send-email-broonie@opensource.wolfsonmicro.com>

On Wed, 2011-05-11 at 10:47 +0200, Mark Brown wrote:
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>  drivers/mfd/Kconfig |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index c78865e..0131d49 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -673,7 +673,7 @@ config MFD_OMAP_USB_HOST
>  
>  config MFD_TPS65910
>  	bool "TPS65910 Power Management chip"
> -	depends on I2C && GPIOLIB
> +	depends on I2C=y && GPIOLIB
>  	select MFD_CORE
>  	help
>  	  if you say yes here you get support for the TPS65910 series of

Thanks, Applied the exact same patch from Jorge (sent a few hours
before).

Thanks

Liam 

  reply	other threads:[~2011-05-11 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  2:44 linux-next: build failure after merge of the voltage tree Stephen Rothwell
2011-05-10  8:38 ` Liam Girdwood
2011-05-10 17:30   ` Jorge Eduardo Candelaria
2011-05-10 19:57     ` Liam Girdwood
2011-05-11  2:27     ` Stephen Rothwell
2011-05-11  6:43       ` Jorge Eduardo Candelaria
2011-05-11 13:29         ` Liam Girdwood
2011-05-11  8:47       ` [PATCH] mfd: TPS65910 depends on I2C and must be built in Mark Brown
2011-05-11 13:35         ` Liam Girdwood [this message]
2011-05-11 13:36           ` Mark Brown

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=1305120918.3277.16.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gg@slimlogic.co.uk \
    --cc=jedu@slimlogic.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).