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/6][pull request] Intel Wired LAN Driver Updates
Date: Tue, 17 Jul 2012 19:20:39 -0700 [thread overview]
Message-ID: <1342578045-17778-1-git-send-email-jeffrey.t.kirsher@intel.com> (raw)
This series contains updates to ixgbe & ixgbevf.
The following are changes since commit 5abf7f7e0f6bdbfcac737f636497d7016d9507eb:
ipv4: fix rcu splat
and are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net-next master
Alexander Duyck (6):
ixgbe: Ping the VFs on link status change to trigger link change
ixgbe: Handle failures in the ixgbe_setup_rx/tx_resources calls
ixgbe: Move configuration of set_real_num_rx/tx_queues into open
ixgbe: Update the logic for ixgbe_cache_ring_dcb and DCB RSS
configuration
ixgbe: Cleanup logic for MRQC and MTQC configuration
ixgbevf: Update descriptor macros to accept pointers and drop _ADV
suffix
drivers/net/ethernet/intel/ixgbe/ixgbe_lib.c | 138 ++++++---------
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 190 +++++++++++++--------
drivers/net/ethernet/intel/ixgbevf/ixgbevf.h | 12 +-
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 18 +-
4 files changed, 183 insertions(+), 175 deletions(-)
--
1.7.10.4
next reply other threads:[~2012-07-18 2:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 2:20 Jeff Kirsher [this message]
2012-07-18 2:20 ` [net-next 1/6] ixgbe: Ping the VFs on link status change to trigger link change Jeff Kirsher
2012-07-18 2:20 ` [net-next 2/6] ixgbe: Handle failures in the ixgbe_setup_rx/tx_resources calls Jeff Kirsher
2012-07-18 2:20 ` [net-next 3/6] ixgbe: Move configuration of set_real_num_rx/tx_queues into open Jeff Kirsher
2012-07-18 2:20 ` [net-next 4/6] ixgbe: Update the logic for ixgbe_cache_ring_dcb and DCB RSS configuration Jeff Kirsher
2012-07-18 2:20 ` [net-next 5/6] ixgbe: Cleanup logic for MRQC and MTQC configuration Jeff Kirsher
2012-07-18 2:20 ` [net-next 6/6] ixgbevf: Update descriptor macros to accept pointers and drop _ADV suffix Jeff Kirsher
2012-07-18 16:21 ` [net-next 0/6][pull request] Intel Wired LAN Driver Updates David Miller
-- strict thread matches above, loose matches on Subject: below --
2013-11-01 13:56 Jeff Kirsher
2013-11-02 5:17 ` David Miller
2012-11-01 10:44 Jeff Kirsher
2012-11-01 15:16 ` David Miller
2012-11-01 20:45 ` Jeff Kirsher
2012-11-02 22:46 ` David Miller
2012-09-24 9:00 Jeff Kirsher
2012-09-24 17:48 ` David Miller
2012-09-17 9:21 Jeff Kirsher
2012-09-17 16:44 ` David Miller
2012-09-05 23:35 Jeff Kirsher
2012-09-06 8:13 ` Richard Cochran
2012-09-10 22:58 ` Vick, Matthew
2012-09-13 21:05 ` Jeff Kirsher
2012-09-17 4:53 ` David Miller
2012-08-21 8:37 Jeff Kirsher
2012-08-22 21:24 ` David Miller
2012-07-20 21:43 Jeff Kirsher
2012-07-21 17:37 ` Jeff Kirsher
2012-06-14 10:18 Jeff Kirsher
2012-06-15 22:38 ` David Miller
2012-04-27 9:36 Jeff Kirsher
2012-04-29 2:08 ` David Miller
2012-04-14 9:16 Jeff Kirsher
2012-04-14 19:18 ` David Miller
2011-12-03 11:44 Jeff Kirsher
2011-10-17 11:32 Jeff Kirsher
2011-10-14 6:21 Jeff Kirsher
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=1342578045-17778-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).