From: Felipe Balbi <felipe.balbi-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Peter Chen <hzpeterchen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kbuild test robot
<fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
kbuild-all-JC7UmRfGjtg@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [balbi-usb:testing/next 64/67] otg.c:undefined reference to `usb_gadget_vbus_disconnect'
Date: Mon, 13 Jun 2016 08:50:39 +0300 [thread overview]
Message-ID: <87vb1d4oy8.fsf@linux.intel.com> (raw)
In-Reply-To: <20160612023955.GA22054@shlinux2>
[-- Attachment #1: Type: text/plain, Size: 2586 bytes --]
Hi,
Peter Chen <hzpeterchen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> On Wed, Jun 08, 2016 at 12:59:51PM +0300, Felipe Balbi wrote:
>>
>> Hi,
>>
>> kbuild test robot <fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> writes:
>> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git testing/next
>> > head: fc4d1f3f522648d92d0c046beedbc1469979499a
>> > commit: 74e51eb7b5b4f7ab33c099c20def3dce0c699006 [64/67] usb: gadget: move gadget API functions to udc-core
>> > config: i386-randconfig-h1-06081244 (attached as .config)
>> > compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
>> > reproduce:
>> > git checkout 74e51eb7b5b4f7ab33c099c20def3dce0c699006
>> > # save the attached .config to linux build tree
>> > make ARCH=i386
>> >
>> > All errors (new ones prefixed by >>):
>> >
>> > drivers/built-in.o: In function `nop_set_peripheral':
>> > phy-generic.c:(.text+0x59f7a6): undefined reference to `usb_gadget_vbus_connect'
>> > drivers/built-in.o: In function `nop_gpio_vbus_thread':
>> > phy-generic.c:(.text+0x59f8a1): undefined reference to `usb_gadget_vbus_connect'
>> > phy-generic.c:(.text+0x59f925): undefined reference to `usb_gadget_vbus_disconnect'
>> > drivers/built-in.o: In function `gpio_vbus_set_peripheral':
>> > phy-gpio-vbus-usb.c:(.text+0x59ff45): undefined reference to `usb_gadget_vbus_disconnect'
>> > drivers/built-in.o: In function `gpio_vbus_work':
>> > phy-gpio-vbus-usb.c:(.text+0x5a02dd): undefined reference to `usb_gadget_vbus_disconnect'
>> > phy-gpio-vbus-usb.c:(.text+0x5a0333): undefined reference to `usb_gadget_vbus_connect'
>> > drivers/built-in.o: In function `ci_handle_vbus_change.part.6':
>> >>> otg.c:(.text+0x605e3b): undefined reference to `usb_gadget_vbus_disconnect'
>> >>> otg.c:(.text+0x605e49): undefined reference to `usb_gadget_vbus_connect'
>> > drivers/built-in.o: In function `isp1704_charger_work':
>> > isp1704_charger.c:(.text+0x648335): undefined reference to `usb_gadget_disconnect'
>> > isp1704_charger.c:(.text+0x64839d): undefined reference to `usb_gadget_connect'
>> > drivers/built-in.o: In function `isp1704_charger_probe':
>> > isp1704_charger.c:(.text+0x648760): undefined reference to `usb_gadget_disconnect'
>>
>> thanks, fixed:
>>
>
> Hi Felipe,
>
> Your patch does not fix above issue, I have tried. At least, I can
> reproduce phy-gpio-vbus-usb build error if it is build in, and
> USB_GADGET is module.
alright, I'll look at this today.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-06-13 5:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 8:34 [balbi-usb:testing/next 64/67] otg.c:undefined reference to `usb_gadget_vbus_disconnect' kbuild test robot
[not found] ` <201606081642.T1wpsuI1%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-06-08 9:59 ` Felipe Balbi
[not found] ` <87k2i09f1k.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-06-12 2:39 ` Peter Chen
2016-06-13 5:50 ` Felipe Balbi [this message]
2016-06-13 6:01 ` Felipe Balbi
[not found] ` <87r3c14ofg.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-06-13 6:48 ` Peter Chen
2016-06-21 1:18 ` Sebastian Reichel
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=87vb1d4oy8.fsf@linux.intel.com \
--to=felipe.balbi-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=hzpeterchen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.