From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com
Subject: [net 0/4][pull request] Intel Wired LAN Drive Update
Date: Sat, 13 Aug 2011 02:23:36 -0700 [thread overview]
Message-ID: <1313227420-9974-1-git-send-email-jeffrey.t.kirsher@intel.com> (raw)
The following series contains updates to e1000e and ixgbe.
The following are changes since commit d80bcf46f1dae47805260dc60fb900cc4dabe35e:
Merge branch 'for-davem' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless
and are available in the git repository at:
master.kernel.org:/pub/scm/linux/kernel/git/jkirsher/net master
Alexander Duyck (1):
ixgbe: Fix FCOE memory leak for DDP packets
Bruce Allan (3):
e1000e: Spurious interrupts & dropped packets with 82577/8/9 in
half-duplex
e1000e: workaround for packet drop on 82579 at 100Mbps
e1000e: workaround invalid Tx/Rx tail descriptor register write
drivers/net/e1000e/e1000.h | 4 ++
drivers/net/e1000e/ich8lan.c | 65 ++++++++++++++++++++++++++------
drivers/net/e1000e/netdev.c | 80 ++++++++++++++++++++++++++++++++++++++--
drivers/net/ixgbe/ixgbe_main.c | 4 +-
4 files changed, 135 insertions(+), 18 deletions(-)
--
1.7.6
next reply other threads:[~2011-08-13 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 9:23 Jeff Kirsher [this message]
2011-08-13 9:23 ` [net 1/4] ixgbe: Fix FCOE memory leak for DDP packets Jeff Kirsher
2011-08-13 9:23 ` [net 2/4] e1000e: Spurious interrupts & dropped packets with 82577/8/9 in half-duplex Jeff Kirsher
2011-08-13 9:23 ` [net 3/4] e1000e: workaround for packet drop on 82579 at 100Mbps Jeff Kirsher
2011-08-13 9:23 ` [net 4/4] e1000e: workaround invalid Tx/Rx tail descriptor register write Jeff Kirsher
2011-08-13 9:26 ` [net 0/4][pull request] Intel Wired LAN Drive Update David Miller
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=1313227420-9974-1-git-send-email-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.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