From: Felipe Balbi <balbi@ti.com>
To: Jim Davis <jim.epost@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>, balbi <balbi@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
grant.likely@linaro.org, Rob Herring <robh+dt@kernel.org>,
linux-usb <linux-usb@vger.kernel.org>,
linux-omap@vger.kernel.org
Subject: Re: randconfig build error with next-20140304, in drivers/usb/dwc3/core.c
Date: Tue, 4 Mar 2014 09:18:50 -0600 [thread overview]
Message-ID: <20140304151850.GF15233@saruman.home> (raw)
In-Reply-To: <CA+r1Zhg3iv4RxC=bWenE+bX=9He6DhfFBXM3L=GOc-Uv=Mxf=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
Hi,
On Tue, Mar 04, 2014 at 07:30:20AM -0700, Jim Davis wrote:
> Building with the attached random configuration file,
>
> warning: (USB_OTG_FSM && FSL_USB2_OTG && USB_MV_OTG) selects USB_OTG
> which has unmet direct dependencies (USB_SUPPORT && USB && PM_RUNTIME)
> warning: (USB_OTG_FSM && FSL_USB2_OTG && USB_MV_OTG) selects USB_OTG
> which has unmet direct dependencies (USB_SUPPORT && USB && PM_RUNTIME)
>
> LD init/built-in.o
> drivers/built-in.o: In function `dwc3_setup_scratch_buffers':
> /home/jim/linux/drivers/usb/dwc3/core.c:280: undefined reference to
> `dwc3_send_gadget_generic_command'
> /home/jim/linux/drivers/usb/dwc3/core.c:287: undefined reference to
> `dwc3_send_gadget_generic_command'
> make: *** [vmlinux] Error 1
will fix it now. Damn, I do 200 randconfigs every week and never caught
that, good job ;-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-03-04 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 14:30 randconfig build error with next-20140304, in drivers/usb/dwc3/core.c Jim Davis
2014-03-04 15:18 ` Felipe Balbi [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=20140304151850.GF15233@saruman.home \
--to=balbi@ti.com \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@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