From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, rjw@sisk.pl
Subject: Re: linux-next: build failure after merge of the final tree
Date: Wed, 17 Mar 2010 23:21:38 -0700 (PDT) [thread overview]
Message-ID: <20100317.232138.183064506.davem@davemloft.net> (raw)
In-Reply-To: <20100318160220.b7eaded6.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 18 Mar 2010 16:02:20 +1100
> Caused by commit 23606cf5d1192c2b17912cb2ef6e62f9b11de133 ("e1000e /
> PCI / PM: Add basic runtime PM support (rev. 4)") from the net tree.
I have a fix for this pushed to net-next-2.6 and I'm sure
Tom will have a fix for the rps UP build failure soon too.
Thanks!
next parent reply other threads:[~2010-03-18 6:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100318160220.b7eaded6.sfr@canb.auug.org.au>
2010-03-18 6:21 ` David Miller [this message]
2010-04-08 5:35 linux-next: build failure after merge of the final tree Stephen Rothwell
2010-04-08 6:25 ` David Miller
2010-04-08 14:15 ` John Linn
2010-04-08 22:59 ` Stephen Rothwell
2010-04-08 23:01 ` John Linn
-- strict thread matches above, loose matches on Subject: below --
2010-05-25 4:10 Stephen Rothwell
2010-05-25 4:58 ` David Miller
2010-05-25 5:14 ` Herbert Xu
2010-05-25 6:56 ` David Miller
2011-05-20 6:18 Stephen Rothwell
2011-05-24 2:06 ` Mike Frysinger
2011-05-24 2:51 ` Greg KH
2011-05-24 3:59 ` Stephen Rothwell
2011-05-24 12:48 ` Greg KH
2011-05-24 21:52 ` Stephen Rothwell
2011-05-24 4:01 ` Linus Torvalds
2011-05-24 4:10 ` Mike Frysinger
2011-05-24 17:10 ` Mike Frysinger
2011-05-24 17:29 ` Linus Torvalds
2011-05-25 9:24 ` Felipe Balbi
2011-05-25 12:13 ` Mike Frysinger
2011-09-30 1:38 Stephen Rothwell
2011-09-30 2:49 ` Yoshihiro Shimoda
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=20100317.232138.183064506.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--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).