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]
Date:	Fri, 26 Apr 2013 15:00:33 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch for-3.8-rc8] usb, chipidea: fix link error when
 USB_EHCI_HCD is a module

On Fri, Apr 26, 2013 at 02:50:56PM -0700, David Rientjes wrote:
> On Fri, 26 Apr 2013, Greg Kroah-Hartman wrote:
> 
> > I think you mean "3.9" in your subject: right?
> > 
> 
> It's your subsystem, if you want to release a kernel with a known-broken 
> config, that's your call.

As you point out, it's been "known broken" since 3.7, no rush now to fix
it, especially so late in the merge window. :)

> > On Fri, Apr 26, 2013 at 01:25:01PM -0700, David Rientjes wrote:
> > > Fixes link error when USB_EHCI_HCD=m and USB_CHIPIDEA_HOST=y:
> > > 
> > > 	drivers/built-in.o: In function `ci_hdrc_host_init':
> > > 	drivers/usb/chipidea/host.c:104: undefined reference to `ehci_init_driver'
> > > 
> > > as a result of commit 09f6ffde2ece ("USB: EHCI: fix build error by making
> > > ChipIdea host a normal EHCI driver").
> > > 
> > > Cc: stable@...r.kernel.org [v3.7+]
> > > Signed-off-by: David Rientjes <rientjes@...gle.com>
> > > ---
> > >  drivers/usb/chipidea/Kconfig | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > There have been a ton of chipidea changes recently in linux-next.  This
> > really just looks like you got the configuration wrong, nothing that is
> > needed at this point in the release cycle, right?
> > 
> 
> This happens in both linux-next as well as Linus's tree, and has since 
> 3.7.

The chipidea maintainer has a big update all queued up in my trees for
3.10-rc1, if you could verify that linux-next fixes your problem, I
would appreciate it.

If not, please let us know.

thanks,

greg k-h
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ