linux-kernel - Re: linux-next: Tree for May 16 (mfd/tpx6586x)

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FB7C310.3010403@xenotime.net>
Date:	Sat, 19 May 2012 08:58:08 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Samuel Ortiz <sameo@...ux.intel.com>
CC:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Mike Rapoport <mike@...pulab.co.il>
Subject: Re: linux-next: Tree for May 16 (mfd/tpx6586x)

On 05/19/2012 07:25 AM, Samuel Ortiz wrote:

> Hi Randy,
> 
> On Wed, May 16, 2012 at 09:16:03AM -0700, Randy Dunlap wrote:
>> On 05/16/2012 03:14 AM, Stephen Rothwell wrote:
>>
>>>
>>> The mfd tree lost its build failure but gained another so I used the
>>> version from next-20120511.
>>>
>>
>>
>>
>> (on i386)
>>
>> drivers/built-in.o: In function `tps6586x_i2c_probe':
>> tps6586x.c:(.devinit.text+0x144e0): undefined reference to `of_regulator_match'
>>
> Is this one fixed now ? It's coming from Mark's regulator tree, not the MFD
> one.


It still fails in linux-next of 20120518.

> Mark, I think mfd/tps6586x.c should select REGULATOR to avoid this one.
> 
> Cheers,
> Samuel.
> 
> 
>> Full randconfig file is attached.
>>
>> -- 
>> ~Randy


-- 
~Randy
--
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/