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, sassmann@redhat.com
Subject: [net-next 0/8][pull request] Intel Wired LAN Driver Updates
Date: Tue, 17 Jul 2012 03:09:11 -0700 [thread overview]
Message-ID: <1342519759-25137-1-git-send-email-jeffrey.t.kirsher@intel.com> (raw)
This series contains updates to ixgbevf.
The following are changes since commit 282f23c6ee343126156dd41218b22ece96d747e3:
tcp: implement RFC 5961 3.2
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net-next master
Alexander Duyck (8):
ixgbevf: Drop all dead or unnecessary code
ixgbevf: Drop netdev_registered value since that is already stored in
netdev
ixgbevf: Make use of NETIF_F_RXCSUM instead of keeping our own flag
ixgbevf: Drop use of eitr_low and eitr_high for hard coded values
ixgbevf: Cleanup accounting for space needed at start of xmit_frame
ixgbevf: Update q_vector to contain ring pointers instead of bitmaps
ixgbevf: Move Tx clean-up into NAPI context
ixgbevf: Use igb style interrupt masks instead of ixgbe style
drivers/net/ethernet/intel/ixgbevf/defines.h | 27 +-
drivers/net/ethernet/intel/ixgbevf/ethtool.c | 13 +-
drivers/net/ethernet/intel/ixgbevf/ixgbevf.h | 99 +--
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 820 ++++++---------------
4 files changed, 276 insertions(+), 683 deletions(-)
--
1.7.10.4
next reply other threads:[~2012-07-17 10:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 10:09 Jeff Kirsher [this message]
2012-07-17 10:09 ` [net-next 1/8] ixgbevf: Drop all dead or unnecessary code Jeff Kirsher
2012-07-17 10:09 ` [net-next 2/8] ixgbevf: Drop netdev_registered value since that is already stored in netdev Jeff Kirsher
2012-07-17 10:09 ` [net-next 3/8] ixgbevf: Make use of NETIF_F_RXCSUM instead of keeping our own flag Jeff Kirsher
2012-07-17 10:09 ` [net-next 4/8] ixgbevf: Drop use of eitr_low and eitr_high for hard coded values Jeff Kirsher
2012-07-17 10:09 ` [net-next 5/8] ixgbevf: Cleanup accounting for space needed at start of xmit_frame Jeff Kirsher
2012-07-17 10:09 ` [net-next 6/8] ixgbevf: Update q_vector to contain ring pointers instead of bitmaps Jeff Kirsher
2012-07-17 10:09 ` [net-next 7/8] ixgbevf: Move Tx clean-up into NAPI context Jeff Kirsher
2012-07-17 10:09 ` [net-next 8/8] ixgbevf: Use igb style interrupt masks instead of ixgbe style Jeff Kirsher
2012-07-17 10:22 ` [net-next 0/8][pull request] Intel Wired LAN Driver Updates David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-01-01 0:53 Jeff Kirsher
2014-01-02 4:01 ` David Miller
2013-09-06 5:43 Jeff Kirsher
2013-09-06 5:58 ` Jeff Kirsher
2013-06-14 3:55 Jeff Kirsher
2013-04-26 4:57 Jeff Kirsher
2013-04-27 3:34 ` David Miller
2012-10-23 10:24 Jeff Kirsher
2012-10-23 17:28 ` David Miller
2012-09-17 4:15 Jeff Kirsher
2012-09-17 4:56 ` David Miller
2012-09-17 8:15 ` Jeff Kirsher
2012-08-31 5:16 Jeff Kirsher
2012-08-31 20:03 ` David Miller
2012-05-04 10:35 Jeff Kirsher
2012-05-04 15:49 ` David Miller
2012-05-01 8:51 Jeff Kirsher
2011-11-16 12:51 Jeff Kirsher
2011-11-16 23:12 ` David Miller
2011-11-16 23:21 ` Jeff Kirsher
2011-11-16 23:32 ` 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=1342519759-25137-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 \
--cc=sassmann@redhat.com \
/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).