public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: Force I2C to be built in when building WM831x
Date: Wed, 25 Nov 2009 00:19:50 +0100	[thread overview]
Message-ID: <20091124231949.GE8290@sortiz.org> (raw)
In-Reply-To: <1259059736-23651-1-git-send-email-broonie@opensource.wolfsonmicro.com>

Hi Mark,

On Tue, Nov 24, 2009 at 10:48:56AM +0000, Mark Brown wrote:
> This works around issues with allmodconfig where it won't propagate the
> dependency from the WM831x core back to the I2C and MFD cores.  When
> doing allmodconfig this causes WM831x to be omitted and ensures that in
> normal builds the dependencies get shaken out.
Applied, thanks for looking at this.

Cheers,
Samuel.


> 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 434bc2f..c33a526 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -183,7 +183,7 @@ config MFD_WM8400
>  config MFD_WM831X
>  	bool "Support Wolfson Microelectronics WM831x/2x PMICs"
>  	select MFD_CORE
> -	depends on I2C
> +	depends on I2C=y
>  	help
>  	  Support for the Wolfson Microelecronics WM831x and WM832x PMICs.
>  	  This driver provides common support for accessing the device,
> -- 
> 1.6.3.3
> 

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

      reply	other threads:[~2009-11-24 23:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 10:48 [PATCH] mfd: Force I2C to be built in when building WM831x Mark Brown
2009-11-24 23:19 ` Samuel Ortiz [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=20091124231949.GE8290@sortiz.org \
    --to=sameo@linux.intel.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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