From: Greg KH <gregkh@linuxfoundation.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 26 (usbcore)
Date: Mon, 26 Mar 2012 11:07:36 -0700 [thread overview]
Message-ID: <20120326180736.GA2893@kroah.com> (raw)
In-Reply-To: <4F70A03C.2070400@xenotime.net>
On Mon, Mar 26, 2012 at 09:58:36AM -0700, Randy Dunlap wrote:
> On 03/25/2012 09:28 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Reminder: please do not add stuff destined for v3.5 to linux-next
> > included trees/branches until after v3.4-rc1 has been released.
> >
> > Changes since 20120323:
>
>
>
> on x86_64:
>
> ERROR: "utf16s_to_utf8s" [drivers/usb/core/usbcore.ko] undefined!
> ERROR: "usb_speed_string" [drivers/usb/core/usbcore.ko] undefined!
>
> Full randconfig file is attached.
Odd, nothing in the usb core has changed in a while in this area,
although we might have gotten some core dependancies mixed up for random
configurations like this.
Any patches would be greatly appreciated...
greg k-h
next prev parent reply other threads:[~2012-03-26 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 4:28 linux-next: Tree for Mar 26 Stephen Rothwell
2012-03-26 16:58 ` linux-next: Tree for Mar 26 (usbcore) Randy Dunlap
2012-03-26 18:07 ` Greg KH [this message]
2012-03-26 20:06 ` Alan Stern
2012-03-26 20:06 ` Alan Stern
2012-03-26 20:16 ` Greg KH
2012-03-28 16:56 ` Randy Dunlap
2012-03-28 23:11 ` Greg KH
2012-03-26 20:38 ` Randy Dunlap
2012-03-26 17:08 ` linux-next: Tree for Mar 26 (platform/x86/apple-gmux) Randy Dunlap
2012-03-26 18:59 ` Seth Forshee
2012-03-26 19:00 ` Matthew Garrett
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=20120326180736.GA2893@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.