linux-kernel - Re: linux-next: build failure after merge of the usb 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <547EA65C.2010605@ti.com>
Date:	Wed, 3 Dec 2014 11:27:48 +0530
From:	Kishon Vijay Abraham I <kishon@...com>
To:	Greg KH <greg@...ah.com>, Stephen Rothwell <sfr@...b.auug.org.au>,
	Heikki Krogerus <heikki.krogerus@...ux.intel.com>
CC:	<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the usb tree

Greg,

On Tuesday 02 December 2014 11:42 PM, Greg KH wrote:
> On Mon, Dec 01, 2014 at 07:19:23PM +1100, Stephen Rothwell wrote:
>> Hi Greg,
>>
>> After merging the usb tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
>>
>> arch/arm/mach-omap2/twl-common.c:94:21: error: array type has incomplete element type
>>  struct phy_consumer consumers[] = {
>>                      ^
>>
>> Caused by commit dbc98635e0d4 ("phy: remove the old lookup method").
>>
>> I have used the usb tree from next-20141128 for today.
> 
> Ick, Heikki and Kishon, do you want me to just revert this patch?  How
> did you test it?

I've resent the patch "arm: omap3: twl: remove usb phy init data" which is
needed to get rid of this error.

This patch was part of the original series sent by Heikki but I couldn't merge
it since I didn't get Ack from tony since it touched arch/arm/mach-omap2/ file.
And I clearly missed the build failure report from fengguang. Sorry.

Thanks
Kishon
--
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/