From: John Youn <John.Youn-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
To: balbi-l0cyMroinI0@public.gmane.org,
Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
Cc: linux-next <linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Build failure: -next 20150316
Date: Tue, 17 Mar 2015 10:41:52 -0700 [thread overview]
Message-ID: <55086760.8060305@synopsys.com> (raw)
In-Reply-To: <20150317035226.GA29805-HgARHv6XitJaoMGHk7MhZQC/G2K4zDHf@public.gmane.org>
On 3/16/2015 8:53 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Mar 16, 2015 at 07:59:04PM +0000, Alan Cox wrote:
>> drivers/built-in.o: In function `dwc2_pci_remove':
>> /rotating/Kernel/next/drivers/usb/dwc2/pci.c:70: undefined reference to
>> `usb_phy_generic_unregister' drivers/built-in.o: In function
>> `dwc2_pci_probe': /rotating/Kernel/next/drivers/usb/dwc2/pci.c:118:
>> undefined reference to
>> `usb_phy_generic_register' /rotating/Kernel/next/drivers/usb/dwc2/pci.c:141:
>> undefined reference to `usb_phy_generic_unregister' Makefile:950: recipe
>> for target 'vmlinux' failed make: *** [vmlinux] Error 1
>
> I think I already a fix for this in my testing/next, just need to mergew
> it into next after testing.
>
>
Hi Felipe,
I think it's different problem. I'll have a patch for you
shortly.
John
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-17 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 19:59 Build failure: -next 20150316 Alan Cox
2015-03-17 3:52 ` Felipe Balbi
[not found] ` <20150317035226.GA29805-HgARHv6XitJaoMGHk7MhZQC/G2K4zDHf@public.gmane.org>
2015-03-17 17:41 ` John Youn [this message]
2015-03-17 17:50 ` Felipe Balbi
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=55086760.8060305@synopsys.com \
--to=john.youn-hkixbcoqz3hwk0htik3j/w@public.gmane.org \
--cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=linux-next-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 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).