linux-kernel - Re: linux-next: build failure after merge of the voltage tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4DE015F0.7090601@oracle.com>
Date:	Fri, 27 May 2011 14:21:52 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Liam Girdwood <lrg@...nel.org>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Jorge Eduardo Candelaria <jedu@...mlogic.co.uk>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Liam Girdwood <lrg@...com>
Subject: Re: linux-next: build failure after merge of the voltage tree

> 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@...cle.com>


> From: Liam Girdwood <lrg@...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@...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 ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/