On Tue, Dec 10, 2013 at 01:10:44PM -0600, Felipe Balbi wrote:
> On Mon, Dec 09, 2013 at 09:09:10PM -0800, Greg KH wrote:
> > On Mon, Dec 09, 2013 at 03:41:41PM -0600, Felipe Balbi wrote:
> > > when any driver using usb_bus_start_enum() is
> > > enabled in a build with CONFIG_USB=m, we will
> > > ha
On Mon, Dec 09, 2013 at 09:09:10PM -0800, Greg KH wrote:
> On Mon, Dec 09, 2013 at 03:41:41PM -0600, Felipe Balbi wrote:
> > when any driver using usb_bus_start_enum() is
> > enabled in a build with CONFIG_USB=m, we will
> > have a build error because of usb_bus_start_enum()
> > will be compiled in
On Mon, Dec 09, 2013 at 03:41:41PM -0600, Felipe Balbi wrote:
> when any driver using usb_bus_start_enum() is
> enabled in a build with CONFIG_USB=m, we will
> have a build error because of usb_bus_start_enum()
> will be compiled into a module (usbcore) and
> the driver (phy-fsm-usb.c or phy-isp130
when any driver using usb_bus_start_enum() is
enabled in a build with CONFIG_USB=m, we will
have a build error because of usb_bus_start_enum()
will be compiled into a module (usbcore) and
the driver (phy-fsm-usb.c or phy-isp1301-omap.c)
will be statically linked to the kernel.
The easiest fix in t
