From: Randy Dunlap <rdunlap@xenotime.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
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 13:38:52 -0700 [thread overview]
Message-ID: <4F70D3DC.6070004@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1203261550290.1179-100000@iolanthe.rowland.org>
On 03/26/2012 01:06 PM, Alan Stern wrote:
> On Mon, 26 Mar 2012, Greg KH wrote:
>
>> 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.
>
> This is puzzling.
>
> utf16s_to_utf8s is defined in fs/nls/nls_base.c,
> which is built according to CONFIG_NLS (in fs/nls/Makefile),
> which is selected by CONFIG_USB (in drivers/usb/Kconfig).
>
> But the config that Randy attached had CONFIG_USB set to M and
> CONFIG_NLS not set. How is that possible?
>
> usb_speed_string is defined in drivers/usb/usb-common.c,
> which is built according to CONFIG_USB_COMMON (in
> drivers/usb/Makefile),
> which defaults to Y if CONFIG_USB_SUPPORT and either
> CONFIG_USB or CONFIG_USB_GADGET is set (in
> drivers/usb/Kconfig).
>
> The problem here was that CONFIG_USB_SUPPORT isn't set but CONFIG_USB
> is set to M. This used not to be possible, since CONFIG_USB was
> defined inside an "if USB_SUPPORT" section. Maybe that got changed and
> needs to be fixed (but
> https://git.kernel.org/?p=linux/kernel/git/next/linux-next.git thinks
> it's still not possible). Or maybe Randy's tree is a little out of
> date.
My tree is just linux-next to Mar. 26.
I'll look into it.
--
~Randy
next prev parent reply other threads:[~2012-03-26 20:38 UTC|newest]
Thread overview: 11+ 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
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 [this message]
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=4F70D3DC.6070004@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stern@rowland.harvard.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).