From: Randy Dunlap <rdunlap@xenotime.net>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: linux-next: Tree for July 17 (mfd/tps65217.c)
Date: Tue, 21 Aug 2012 10:51:37 -0700 [thread overview]
Message-ID: <5033CAA9.9000101@xenotime.net> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA0B471@DBDE01.ent.ti.com>
On 08/05/2012 11:38 PM, AnilKumar, Chimata wrote:
> On Fri, Aug 03, 2012 at 22:58:01, Randy Dunlap wrote:
>> On 07/17/2012 02:48 PM, Randy Dunlap wrote:
>>
>>> On 07/16/2012 10:41 PM, Stephen Rothwell wrote:
>>>
>>>> Hi all,
>>>>
>>>> Changes since 20120716:
>>>>
>>>
>>>
>>> on i386:
>>>
>>> drivers/built-in.o: In function `tps65217_probe':
>>> tps65217.c:(.devinit.text+0x13e37): undefined reference to `of_regulator_match'
>>>
>>>
>>> Full randconfig file is attached.
>>> CONFIG_REGULATOR is not enabled.
>>>
>>
>>
>> This build error is still present in linux-next of 20120803.
>>
>
> This will be fixed with this patch
> https://patchwork.kernel.org/patch/1220151/
>
> Today, I will submit v2 for this
This build still fails in linux-next 20120821.
--
~Randy
next prev parent reply other threads:[~2012-08-21 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 5:41 linux-next: Tree for July 17 Stephen Rothwell
2012-07-17 20:29 ` linux-next: Tree for July 17 (fs/sync.c) Randy Dunlap
2012-07-17 20:51 ` Geert Uytterhoeven
2012-07-17 21:48 ` linux-next: Tree for July 17 (mfd/tps65217.c) Randy Dunlap
2012-08-03 17:28 ` Randy Dunlap
2012-08-06 6:38 ` AnilKumar, Chimata
2012-08-21 17:51 ` Randy Dunlap [this message]
2012-08-22 4:25 ` AnilKumar, Chimata
2012-07-18 9:27 ` linux-next: Tree for July 17 Sedat Dilek
2012-07-18 10:07 ` Stephen Rothwell
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=5033CAA9.9000101@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=anilkumar@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).