From: Randy Dunlap <rdunlap@xenotime.net>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mike Rapoport <mike@compulab.co.il>
Subject: Re: linux-next: Tree for May 16 (mfd/tpx6586x)
Date: Sat, 19 May 2012 08:58:08 -0700 [thread overview]
Message-ID: <4FB7C310.3010403@xenotime.net> (raw)
In-Reply-To: <20120519142506.GN12015@sortiz-mobl>
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
next prev parent reply other threads:[~2012-05-19 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 10:14 linux-next: Tree for May 16 Stephen Rothwell
2012-05-16 16:01 ` linux-next: Tree for May 16 (mfd/mc13xxx) Randy Dunlap
2012-05-16 18:04 ` Uwe Kleine-König
2012-05-18 11:04 ` Samuel Ortiz
2012-05-16 16:16 ` linux-next: Tree for May 16 (mfd/tpx6586x) Randy Dunlap
2012-05-19 14:25 ` Samuel Ortiz
2012-05-19 15:58 ` Randy Dunlap [this message]
2012-05-19 16:53 ` 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=4FB7C310.3010403@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=sameo@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).