From: Greg KH <greg@kroah•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, David Vrabel <david.vrabel@csr•com>
Subject: Re: linux-next: usb.current tree build failure
Date: Tue, 7 Apr 2009 19:20:39 -0700 [thread overview]
Message-ID: <20090408022039.GA13392@kroah.com> (raw)
In-Reply-To: <20090408014830.GA13223@kroah.com>
On Tue, Apr 07, 2009 at 06:48:30PM -0700, Greg KH wrote:
> On Wed, Apr 08, 2009 at 10:10:07AM +1000, Stephen Rothwell wrote:
> > Hi Greg,
> >
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> >
> > drivers/block/ub.c: In function 'ub_scsi_urb_compl':
> > drivers/block/ub.c:1052: error: implicit declaration of function 'usb_settoggle'
> >
> > Caused by commit 876d77e4521ff2b4f937bf7104bf70d2d105b0c2 ("USB: add
> > reset endpoint operations") from the usb.current tree.
> >
> > I have used the version of that tree from next-20090407. (Which means I
> > need to do the same for the driver-core, usb and staring trees that
> > depend on the usb.current tree.)
>
> I think I'll just drop these patches, as this isn't ok.
>
> David, care to respin these and resend them to me? I'll have to drop
> your whole series :(
I've now dropped your 6 patches and pushed out a new series so that
linux-next will build properly with the usb tree in it tomorrow.
Stephen, sorry for the trouble.
greg k-h
next prev parent reply other threads:[~2009-04-08 2:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 0:10 linux-next: usb.current tree build failure Stephen Rothwell
2009-04-08 1:48 ` Greg KH
2009-04-08 2:20 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-07 0:53 Stephen Rothwell
2008-08-07 1:56 ` Kevin Lloyd
2008-08-07 4:23 ` Greg KH
2008-08-07 6:25 ` Stephen Rothwell
2008-08-01 1:20 Stephen Rothwell
2008-08-01 6:12 ` Greg KH
2008-08-01 6:43 ` Stephen Rothwell
2008-08-07 0:56 ` Stephen Rothwell
2008-08-07 4:24 ` 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=20090408022039.GA13392@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=david.vrabel@csr$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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