From: Ingo Molnar <mingo@elte.hu>
To: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
wimax@linuxwimax.org, LKML <linux-kernel@vger.kernel.org>,
linux-wimax@intel.com, linux-next@vger.kernel.org
Subject: Re: linux-next: Tree for January 7 (wimax: more)
Date: Thu, 8 Jan 2009 11:15:01 +0100 [thread overview]
Message-ID: <20090108101501.GA15294@elte.hu> (raw)
In-Reply-To: <200901071051.23010.inaky@linux.intel.com>
* Inaky Perez-Gonzalez <inaky@linux.intel.com> wrote:
> On Wednesday 07 January 2009, Randy Dunlap wrote:
> > Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > The powerpc ppc44x_defconfig builds again.
> > >
> > > Changes since 20090106:
> >
> > drivers/net/wimax/i2400m/usb.c:403: error: 'struct usb_device' has no
> > member named 'autosuspend_delay' drivers/net/wimax/i2400m/usb.c:404: error:
> > 'struct usb_device' has no member named 'autosuspend_disabled'
> > drivers/net/wimax/i2400m/usb.c:506: error: 'struct usb_device' has no
> > member named 'auto_pm'
>
> Fix on the way -- need #ifdef CONFIG_PMs in a few parts.
FYI, this build bug has now hit upstream too:
drivers/net/wimax/i2400m/usb.c: In function 'i2400mu_probe':
drivers/net/wimax/i2400m/usb.c:403: error: 'struct usb_device' has no member named 'autosuspend_delay'
drivers/net/wimax/i2400m/usb.c:404: error: 'struct usb_device' has no member named 'autosuspend_disabled'
drivers/net/wimax/i2400m/usb.c: In function 'i2400mu_suspend':
drivers/net/wimax/i2400m/usb.c:506: error: 'struct usb_device' has no member named 'auto_pm'
Ingo
next prev parent reply other threads:[~2009-01-08 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 6:06 linux-next: Tree for January 7 Stephen Rothwell
2009-01-07 18:01 ` linux-next: Tree for January 7 (wimax: more) Randy Dunlap
2009-01-07 18:51 ` Inaky Perez-Gonzalez
2009-01-08 10:15 ` Ingo Molnar [this message]
2009-01-07 18:08 ` linux-next: Tree for January 7 (ath9k) Randy Dunlap
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=20090108101501.GA15294@elte.hu \
--to=mingo@elte.hu \
--cc=inaky@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wimax@intel.com \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
--cc=wimax@linuxwimax.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).