From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: linux-next: build failure after merge of the staging-next tree
Date: Fri, 30 Apr 2010 07:41:28 -0700 [thread overview]
Message-ID: <20100430144128.GC1824@kroah.com> (raw)
In-Reply-To: <20100430155224.ab570260.sfr@canb.auug.org.au>
On Fri, Apr 30, 2010 at 03:52:24PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/media/video/tlg2300/pd-main.c: In function 'poseidon_probe':
> drivers/media/video/tlg2300/pd-main.c:457: error: 'struct usb_device' has no member named 'autosuspend_disabled'
> drivers/net/wimax/i2400m/usb.c: In function 'i2400mu_probe':
> drivers/net/wimax/i2400m/usb.c:508: error: 'struct usb_device' has no member named 'autosuspend_disabled'
>
> Caused by commit 3a03bb2443e8fb3b35666dc598e7f626519c544a ("USB: use PM
> core routines to enable/disable autosuspend") from the usb tree. I have
> reverted that commit for today.
It would be good to get that back into the tree. Alan, care to fix this
up?
thanks,
greg k-h
next prev parent reply other threads:[~2010-04-30 18:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 5:52 linux-next: build failure after merge of the staging-next tree Stephen Rothwell
2010-04-30 14:41 ` Greg KH [this message]
2010-04-30 16:14 ` [PATCH] USB: remove leftover references to udev->autosuspend_disabled Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2010-04-30 5:52 linux-next: build failure after merge of the staging-next tree Stephen Rothwell
2010-04-30 14:43 ` Greg KH
2010-05-18 5:30 ` Neil Brown
2010-05-21 23:36 ` Greg KH
2010-05-22 0:20 ` Neil Brown
2010-05-22 14:49 ` Greg KH
2010-05-22 15:54 ` Sage Weil
2010-05-01 17:48 ` Greg KH
2010-05-02 4:55 ` Eric W. Biederman
2010-04-30 5:50 Stephen Rothwell
2010-04-30 14:45 ` Greg KH
2010-04-30 15:08 ` Stephen Rothwell
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=20100430144128.GC1824@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stern@rowland.harvard.edu \
/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