From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: "Garzik, Jeff" <jgarzik@pobox.com>
Cc: netdev@vger.kernel.org, "Brandeburg,
Jesse" <jesse.brandeburg@intel.com>,
"Kok, Auke" <auke-jan.h.kok@intel.com>,
"Kok, Auke" <auke@foo-projects.org>,
"Ronciak, John" <john.ronciak@intel.com>
Subject: [PATCH 0/3] e1000: fix, two minor updates
Date: Fri, 16 Feb 2007 14:39:13 -0800 [thread overview]
Message-ID: <20070216223913.26963.76602.stgit@gitlost.site> (raw)
Jeff,
Please pull:
git-pull git://lost.foo-projects.org/~ahkok/git/netdev-2.6 e1000
to receive one fix (patch 1) and 2 updates to the e1000 driver.
Cheers,
Auke
---
Summary:
Jesse Brandeburg <jesse.brandeburg@intel.com>: (1)
e1000: fix shared interrupt warning message
Auke Kok <auke-jan.h.kok@intel.com>: (2)
e1000: allow ethtool to see link status when down
e1000: remove obsolete custom pci_save_state code
---
drivers/net/e1000/e1000.h | 1
drivers/net/e1000/e1000_ethtool.c | 2 -
drivers/net/e1000/e1000_main.c | 70 ++++----------------------------------
3 files changed, 9 insertions(+), 64 deletions(-)
---
These patches appply against torvalds/linux-2.6 #master as of
commit 0187f221e96e3436d552c0c7143f183eb82fb658 ( Ben Dooks --
"[PATCH] s3c2410fb: fix un-initialised dev field")
next reply other threads:[~2007-02-16 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 22:39 Kok, Auke [this message]
2007-02-16 22:39 ` [PATCH 1/3] e1000: fix shared interrupt warning message Kok, Auke
2007-02-17 20:38 ` Jeff Garzik
2007-02-17 20:47 ` Auke Kok
2007-02-17 23:19 ` Francois Romieu
2007-02-18 2:20 ` Auke Kok
2007-02-16 22:39 ` [PATCH 2/3] e1000: remove obsolete custom pci_save_state code Kok, Auke
2007-02-16 22:39 ` [PATCH 3/3] e1000: allow ethtool to see link status when down Kok, Auke
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=20070216223913.26963.76602.stgit@gitlost.site \
--to=auke-jan.h.kok@intel.com \
--cc=auke@foo-projects.org \
--cc=jesse.brandeburg@intel.com \
--cc=jgarzik@pobox.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).