From: Randy Dunlap <rdunlap@infradead.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: linux-next: Tree for May 29 (usb/gadget/udc/aspeed-vhub)
Date: Wed, 6 Jun 2018 08:30:55 -0700 [thread overview]
Message-ID: <be9159d4-f53e-1f1a-e87b-dfd55c458c9a@infradead.org> (raw)
In-Reply-To: <3731dd7511b6a0ee74b062caf616e8041382fb90.camel@kernel.crashing.org>
On 05/29/2018 03:16 PM, Benjamin Herrenschmidt wrote:
> On Tue, 2018-05-29 at 10:04 -0700, Randy Dunlap wrote:
>> On 05/29/2018 03:44 AM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20180525:
>>>
>>
>> on i386:
>>
>> when builtin:
>> drivers/usb/gadget/udc/aspeed-vhub/hub.o: In function `ast_vhub_std_hub_request':
>> hub.c:(.text+0x3aa): undefined reference to `usb_gadget_get_string'
>>
>> or when modular:
>> ERROR: "usb_gadget_get_string" [drivers/usb/gadget/udc/aspeed-vhub/aspeed-vhub.ko] undefined!
>>
>>
>> Full randconfig for modular build is attached.
>
> Somebody already sent a fix for this. Thanks. (Missing a dependency on
> LIBCOMPOSITE).
Hi,
linux-next is still having this build error.
Can we get that fix merged somewhere, please?
thanks,
--
~Randy
prev parent reply other threads:[~2018-06-06 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 10:44 linux-next: Tree for May 29 Stephen Rothwell
2018-05-29 17:04 ` linux-next: Tree for May 29 (usb/gadget/udc/aspeed-vhub) Randy Dunlap
2018-05-29 22:16 ` Benjamin Herrenschmidt
2018-06-06 15:30 ` Randy Dunlap [this message]
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=be9159d4-f53e-1f1a-e87b-dfd55c458c9a@infradead.org \
--to=rdunlap@infradead.org \
--cc=benh@kernel.crashing.org \
--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 \
/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).