From: Greg KH <greg@kroah•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, Alan Stern <stern@rowland•harvard.edu>
Subject: Re: linux-next: usb.current tree build failure
Date: Thu, 31 Jul 2008 23:12:50 -0700 [thread overview]
Message-ID: <20080801061250.GB8634@kroah.com> (raw)
In-Reply-To: <20080801112021.547dfaea.sfr@canb.auug.org.au>
On Fri, Aug 01, 2008 at 11:20:21AM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> drivers/built-in.o: In function `.usb_reset_device':
> (.text+0x1bfeb4): undefined reference to `.usb_forced_unbind_intf'
> drivers/built-in.o: In function `.usb_reset_device':
> (.text+0x1c03b8): undefined reference to `.usb_rebind_intf'
>
> Caused by commit 78d9a487ee961c356e1a934d9a92eca38ffb3a70 ("USB: Force
> unbinding of drivers lacking reset_resume or other methods").
>
> The above config has CONFIG_USB=y and CONFIG_PM not set.
>
> I applied the following (probably incorrect) patch.
Thanks, this is my fault, I applied the wrong patch from Alan (he sent
me a later more correct version.) Should be fixed in the tree for
tomorrow.
greg k-h
next prev parent reply other threads:[~2008-08-01 6:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 1:20 linux-next: usb.current tree build failure Stephen Rothwell
2008-08-01 6:12 ` Greg KH [this message]
2008-08-01 6:43 ` Stephen Rothwell
2008-08-07 0:56 ` Stephen Rothwell
2008-08-07 4:24 ` Greg KH
2008-08-07 17:04 ` [PATCH] USB: fix compiler warning fix Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2008-08-07 0:53 linux-next: usb.current tree build failure Stephen Rothwell
2008-08-07 1:56 ` Kevin Lloyd
2008-08-07 4:23 ` Greg KH
2008-08-07 6:25 ` Stephen Rothwell
2009-04-08 0:10 Stephen Rothwell
2009-04-08 1:48 ` Greg KH
2009-04-08 2:20 ` Greg KH
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=20080801061250.GB8634@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=stern@rowland$(echo .)harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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