[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131209210101.GC29143@saruman.home>
Date: Mon, 9 Dec 2013 15:01:01 -0600
From: Felipe Balbi <balbi@...com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Felipe Balbi <balbi@...com>, <linux-next@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
Anton Tikhomirov <av.tikhomirov@...sung.com>
Subject: Re: linux-next: build failure after merge of the usb-gadget tree
On Tue, Dec 10, 2013 at 07:43:30AM +1100, Stephen Rothwell wrote:
> Hi Felipe,
>
> On Mon, 9 Dec 2013 13:40:32 -0600 Felipe Balbi <balbi@...com> wrote:
> >
> > On Sun, Dec 08, 2013 at 10:11:52PM -0600, Felipe Balbi wrote:
> > > On Mon, Dec 09, 2013 at 02:58:03PM +1100, Stephen Rothwell wrote:
> > > >
> > > > After merging the usb-gadget tree, today's linux-next build (x86_64
> > > > allmodconfig) failed like this:
> > > >
> > > > drivers/built-in.o: In function `otg_set_state':
> > > > (.text+0x14f7de): undefined reference to `usb_bus_start_enum'
> > > >
> > > > CONFIG_USB is 'm' in this build.
> > > >
> > > > I am not sure what changed to cause this, maybe e1d2e31975e1 ("usb: phy:
> > > > Add OTG FSM configuration option")?
> > > >
> > > > I have used the usb-gadget tree from next-20131206 for today.
> > >
> > > I see what caused it, will fix it up with a patch which should probably
> > > be backported a few kernels back. Thanks for letting me know.
> >
> > Do you still have the .config which caused that build error ? I couldn't
> > reproduce with CONFIG_USB=m && CONFIG_USB_OTG=y.
>
> See above, it was just an x86_64 allmodconfig build.
cool, building that on my end.
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists