netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
	jogreene@redhat.com
Subject: [net-next 0/6][pull request] Intel Wired LAN Driver Updates 2015-03-27
Date: Fri, 27 Mar 2015 03:02:46 -0700	[thread overview]
Message-ID: <1427450573-13945-1-git-send-email-jeffrey.t.kirsher@intel.com> (raw)

This series contains updates to i40e and i40evf.

Jesse adds new device IDs to handle the new 20G speed for KR2.

Mitch provides a fix for an issue that shows up as a panic or memory
corruption when the device is brought down while under heavy stress.
This is resolved by delaying the releasing of resources until we
receive acknowledgment from the PF driver that the rings have indeed
been stopped.  Also adds firmware version information to ethtool
reporting to align with ixgbevf behavior.

Akeem increases the polling loop limiter, sine we found that in
certain circumstances the firmware can take longer to be ready after
a reset.

The following are changes since commit 5a352dd0a3aac03b443c94828dfd7144261c8636:
  ipv6: hash net ptr into fragmentation bucket selection
and are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue master

master

Akeem G Abodunrin (1):
  i40e: Increase PF reset max loop limit

Catherine Sullivan (1):
  i40e: Bump version to 1.2.43

Jesse Brandeburg (1):
  i40e/i40evf: implement KR2 support

Mitch Williams (3):
  i40evf: delay releasing rings
  i40evf: resequence close operations
  i40evf: add FW version to ethtool info

 drivers/net/ethernet/intel/i40e/i40e_common.c      |  4 ++-
 drivers/net/ethernet/intel/i40e/i40e_ethtool.c     | 16 +++++++++++
 drivers/net/ethernet/intel/i40e/i40e_main.c        |  6 +++-
 drivers/net/ethernet/intel/i40e/i40e_type.h        |  1 +
 drivers/net/ethernet/intel/i40evf/i40e_common.c    |  1 +
 drivers/net/ethernet/intel/i40evf/i40e_type.h      |  3 +-
 drivers/net/ethernet/intel/i40evf/i40evf.h         |  2 ++
 drivers/net/ethernet/intel/i40evf/i40evf_ethtool.c |  2 +-
 drivers/net/ethernet/intel/i40evf/i40evf_main.c    | 33 +++++++++-------------
 .../net/ethernet/intel/i40evf/i40evf_virtchnl.c    |  2 ++
 10 files changed, 46 insertions(+), 24 deletions(-)

-- 
1.9.3

             reply	other threads:[~2015-03-27 10:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 10:02 Jeff Kirsher [this message]
2015-03-27 10:02 ` [net-next 1/6] i40e/i40evf: implement KR2 support Jeff Kirsher
2015-03-27 10:02 ` [net-next 2/6] i40evf: delay releasing rings Jeff Kirsher
2015-03-27 10:02 ` [net-next 3/6] i40evf: resequence close operations Jeff Kirsher
2015-03-27 10:02 ` [net-next 4/6] i40e: Increase PF reset max loop limit Jeff Kirsher
2015-03-27 10:02 ` [net-next 4/6] i40e: Increase pf " Jeff Kirsher
2015-03-27 10:02 ` [net-next 5/6] i40evf: add FW version to ethtool info Jeff Kirsher
2015-03-27 10:02 ` [net-next 6/6] i40e: Bump version to 1.2.43 Jeff Kirsher
2015-03-29 20:38 ` [net-next 0/6][pull request] Intel Wired LAN Driver Updates 2015-03-27 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=1427450573-13945-1-git-send-email-jeffrey.t.kirsher@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --cc=jogreene@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --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).