From: Felipe Balbi <balbi@ti.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Jim Davis <jim.epost@gmail.com>,
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>,
linux-usb <linux-usb@vger.kernel.org>
Subject: Re: randconfig build error with next-20141201, in drivers/usb/musb/tusb6010.c
Date: Tue, 2 Dec 2014 13:18:36 -0600 [thread overview]
Message-ID: <20141202191836.GN26934@saruman> (raw)
In-Reply-To: <20141202181316.GE11700@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
Hi,
On Tue, Dec 02, 2014 at 10:13:16AM -0800, Greg Kroah-Hartman wrote:
> On Mon, Dec 01, 2014 at 10:00:35AM -0700, Jim Davis wrote:
> > Building with the attached random configuration file,
> >
> > drivers/built-in.o: In function `tusb_remove':
> > tusb6010.c:(.text+0x16a817): undefined reference to `usb_phy_generic_unregister'
> > drivers/built-in.o: In function `tusb_probe':
> > tusb6010.c:(.text+0x16b24e): undefined reference to `usb_phy_generic_register'
> > make: *** [vmlinux] Error 1
>
> This looks like a phy issue, Kishon and Heikki?
Tony Lindgren sent a patch adding a few dependencies to MUSB's Kconfig.
This bug has been there forever though, so I'll merge Tony's fix during
3.19-rc1.
No clue how come I never got this as I always run 300 randconfigs on my
pull requests before sending them to you.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-12-02 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 17:00 randconfig build error with next-20141201, in drivers/usb/musb/tusb6010.c Jim Davis
2014-12-02 18:13 ` Greg Kroah-Hartman
2014-12-02 19: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=20141202191836.GN26934@saruman \
--to=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jim.epost@gmail.com \
--cc=kishon@ti.com \
--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).