From: Randy Dunlap <randy.dunlap@oracle.com>
To: Liam Girdwood <lrg@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: linux-next: build failure after merge of the voltage tree
Date: Fri, 27 May 2011 14:21:52 -0700 [thread overview]
Message-ID: <4DE015F0.7090601@oracle.com> (raw)
In-Reply-To: <1306530788.3366.30.camel@odin>
> Hi,
>
> gah, looks this was broken by moving the tps65910 gpio directory move.
>
> This should fix it though:-
It does. Thanks.
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
> From: Liam Girdwood <lrg@ti.com>
> Date: Fri, 27 May 2011 22:06:52 +0100
> Subject: [PATCH] mfd: tps65910 - fix build breakage caused by tps65910 gpio directory move.
>
> Signed-off-by: Liam Girdwood <lrg@ti.com>
> ---
> drivers/mfd/Kconfig | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
> index b6c2677..0f09c05 100644
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig
> @@ -721,7 +721,7 @@ config MFD_PM8XXX_IRQ
>
> config MFD_TPS65910
> bool "TPS65910 Power Management chip"
> - depends on I2C=y
> + depends on I2C=y && GPIOLIB
> select MFD_CORE
> select GPIO_TPS65910
> help
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-05-27 21:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201105271759.p4RHxa2X008919@hera.kernel.org>
2011-05-27 19:58 ` linux-next: build failure after merge of the voltage tree Randy Dunlap
2011-05-27 21:13 ` Liam Girdwood
2011-05-27 21:21 ` Randy Dunlap [this message]
2011-05-10 2:44 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
-- strict thread matches above, loose matches on Subject: below --
2010-12-15 2:09 Stephen Rothwell
2010-12-15 9:04 ` Liam Girdwood
2010-12-15 14:03 ` Mark Brown
2010-12-14 4:49 Stephen Rothwell
2010-12-14 5:10 ` Yong Shen
2010-12-14 15:56 ` Liam Girdwood
2010-12-15 2:03 ` Yong Shen
2010-11-11 0:36 Stephen Rothwell
2010-11-11 11:46 ` Mark Brown
2010-11-11 12:09 ` Liam Girdwood
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=4DE015F0.7090601@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jedu@slimlogic.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@kernel.org \
--cc=lrg@ti.com \
--cc=sameo@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.