From: kishon@ti•com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists•infradead.org
Subject: linux-next ARM multi-platform randconfig errors
Date: Mon, 22 Apr 2013 18:15:25 +0530 [thread overview]
Message-ID: <517530E5.5050901@ti.com> (raw)
In-Reply-To: <20130422115243.GD10797@arwen.pp.htv.fi>
Hi,
On Monday 22 April 2013 05:22 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Apr 22, 2013 at 11:21:49AM +0300, Felipe Balbi wrote:
>>> -Kevin Hilman <khilman@ti•com>
>>> +Kevin Hilman <khilman@deeprootsystems•com>
>>>
>>> On 04/19/2013 07:12 PM, Tony Lindgren wrote:
>>>> * Rob Herring <robherring2@gmail•com> [130418 20:11]:
>>>>> Current errors in linux-next for ARM multi-platform randconfig builds.
>>>>>
>>>>> Rob
>>>>>
>>>>> arch/arm/mach-omap2/built-in.o:dss-common.c:(.init.text+0x6830): more undefined references to `usb_bind_phy' follow
>>>>
>>>> Felipe & Roger, can you guys take a look at the usb_bind_phy issue
>>>> in linux next? I have not seen that in the multiplatform randconfigs
>>>> I've built, but I have had some omap2+ specific things enabled there.
>>>
>>> These problems happen if USB_PHY is not enabled as a built-in driver.
>>> I had pointed this out earlier [1] and Felipe should have a fix for it.
>>
>> yeah, ideally we wouldn't do any 'select' and just update defconfig with
>> the necessary changes. We need the patch below to update defconfig and
>> another patch to stub out usb_bind_phy when !USB_PHY.
>
> the stub is already there, this should fix the other part though:
Denis had sent a patch for it 4 days back [1]. Lets use that instead.
Thanks
Kishon
[1] - https://patchwork.kernel.org/patch/2460691/
next prev parent reply other threads:[~2013-04-22 12:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 3:06 linux-next ARM multi-platform randconfig errors Rob Herring
2013-04-19 16:12 ` Tony Lindgren
2013-04-19 16:41 ` Tomi Valkeinen
2013-04-19 19:43 ` Tony Lindgren
2013-04-19 19:51 ` Tony Lindgren
2013-04-19 20:11 ` Arnd Bergmann
2013-04-19 20:40 ` Tony Lindgren
2013-04-19 20:58 ` Arnd Bergmann
[not found] ` <20130419215134.GY10155@atomide.com>
2013-04-19 22:08 ` Arnd Bergmann
2013-04-19 22:53 ` Paul Walmsley
2013-04-19 21:02 ` Tony Lindgren
2013-04-19 21:09 ` Tony Lindgren
2013-04-19 19:52 ` Jon Hunter
2013-04-19 20:42 ` Tony Lindgren
2013-04-19 17:23 ` Tony Lindgren
2013-04-22 7:23 ` Roger Quadros
2013-04-22 8:21 ` Felipe Balbi
2013-04-22 11:52 ` Felipe Balbi
2013-04-22 12:45 ` Kishon Vijay Abraham I [this message]
2013-04-22 13:04 ` Felipe Balbi
2013-04-22 17:32 ` Mikulas Patocka
2013-04-22 22:57 ` Rob Herring
2013-05-13 22:37 ` [PATCH] bcache: Fix link errors on ARM Mikulas Patocka
2013-04-22 18:59 ` linux-next ARM multi-platform randconfig errors Mike Turquette
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=517530E5.5050901@ti.com \
--to=kishon@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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