From: Borislav Petkov <bp@alien8.de>
To: jeffrey.t.kirsher@intel.com
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Jiri Slaby <jslaby@suse.cz>,
Bjorn Helgaas <bhelgaas@google.com>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
x86@kernel.org, lkml <linux-kernel@vger.kernel.org>,
e1000-devel@lists.sourceforge.net,
Bruce Allan <bruce.w.allan@intel.com>
Subject: Re: e1000e + suspend, 3.9-rc2
Date: Mon, 11 Mar 2013 21:25:37 +0100 [thread overview]
Message-ID: <20130311202537.GF5000@pd.tnic> (raw)
In-Reply-To: <513E355C.4000204@gmail.com>
On Mon, Mar 11, 2013 at 12:49:48PM -0700, Jeff Kirsher wrote:
> No, the patches have not made it into Linus's tree yet. They are in
> David Miller's net tree, and he just sent a pull request to Linus this
> morning. So expect them to be in 3.9-rc3.
You mean this pull request:
commit 0cb77508252e2d0e00c5ec7e57b4be9b3f7eb24d
Merge: ffb6a445e7cd 9026c4927254
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mon Mar 11 07:51:59 2013 -0700
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
Pull networking fixes from David Miller:
?
Yeah, it is already upstream. And yeah, it did trigger with it.
$ git describe
v3.9-rc2-112-g7c6baa304b84
But it somehow doesn't trigger with that same kernel anymore so I'll
consider it a glitch and watch it over the next days.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-03-11 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 19:19 e1000e + suspend, 3.9-rc2 Borislav Petkov
2013-03-11 19:49 ` Jeff Kirsher
2013-03-11 20:25 ` Borislav Petkov [this message]
2013-03-12 17:17 ` Borislav Petkov
2013-03-19 10:16 ` Jiri Slaby
2013-03-19 10:27 ` Konstantin Khlebnikov
2013-03-19 12:22 ` Jiri Slaby
2013-03-29 18:04 ` Allan, Bruce W
2013-04-15 15:29 ` Jiri Slaby
2013-06-12 19:14 ` Jiri Slaby
2013-06-12 21:29 ` Konstantin Khlebnikov
2013-06-18 11:07 ` Jiri Slaby
2013-07-05 20:24 ` Jiri Slaby
2013-07-15 8:25 ` Jiri Slaby
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=20130311202537.GF5000@pd.tnic \
--to=bp@alien8.de \
--cc=bhelgaas@google.com \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jslaby@suse.cz \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=x86@kernel.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