Netdev List
 help / color / mirror / Atom feed
From: Nathan Fontenot <nfont@linux.vnet.ibm.com>
To: netdev@vger.kernel.org
Cc: brking@linux.vnet.ibm.com, jallen@linux.vnet.ibm.com,
	muvic@linux.vnet.ibm.com, tlfalcon@linux.vnet.ibm.com
Subject: [PATCH net-next 00/11] ibmvnic: Updated reset handler and code fixes
Date: Sat, 29 Apr 2017 04:15:27 -0400	[thread overview]
Message-ID: <20170429080710.13438.39798.stgit@ltcalpine2-lp23.aus.stglabs.ibm.com> (raw)

This set of patches multiple code fixes and a new rest handler
for the ibmvnic driver. In order to implement the new reset handler
for the ibmvnic driver resource initialization needed to be moved to
its own routine, a state variable is introduced to replace the
various is_* flags in the driver, and a new routine to handle the
assorted reasons the driver can be reset.

The additional patches cleanup some of the code, renmove some
memory leaks, and fix a few bugs.

---

Nathan Fontenot (10):
      ibmvnic: Move resource initialization to its own routine
      ibmvnic: Replace is_closed with state field
      ibmvnic: Updated reset handling
      ibmvnic: Delete napi's when releasing driver resources
      ibmvnic: Whitespace correction in release_rx_pools
      ibmvnic: Clean up tx pools when closing
      ibmvnic: Wait for any pending scrqs entries at driver close
      ibmvnic: Check for driver reset first in ibmvnic_xmit
      ibmvnic: Continue skb processing after skb completion error
      ibmvnic: Move queue restart

Thomas Falcon (1):
      From: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>


 drivers/net/ethernet/ibm/ibmvnic.c |  564 +++++++++++++++++++++++-------------
 drivers/net/ethernet/ibm/ibmvnic.h |   31 ++
 2 files changed, 390 insertions(+), 205 deletions(-)

             reply	other threads:[~2017-04-29  4:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29  8:15 Nathan Fontenot [this message]
2017-04-29  8:15 ` [PATCH net-next 01/11] ibmvnic: Move resource initialization to its own routine Nathan Fontenot
2017-04-29  8:15 ` [PATCH net-next 02/11] ibmvnic: Replace is_closed with state field Nathan Fontenot
2017-04-29  8:15 ` [PATCH net-next 03/11] ibmvnic: Updated reset handling Nathan Fontenot
2017-04-29  8:15 ` [PATCH net-next 04/11] ibmvnic: Delete napi's when releasing driver resources Nathan Fontenot
2017-04-29  8:15 ` [PATCH net-next 05/11] ibmvnic: Whitespace correction in release_rx_pools Nathan Fontenot
2017-04-29  8:16 ` [PATCH net-next 06/11] ibmvnic: Clean up tx pools when closing Nathan Fontenot
2017-04-29  8:16 ` [PATCH net-next 07/11] ibmvnic: Wait for any pending scrqs entries at driver close Nathan Fontenot
2017-04-29  8:16 ` [PATCH net-next 08/11] ibmvnic: Check for driver reset first in ibmvnic_xmit Nathan Fontenot
2017-04-29  8:16 ` [PATCH net-next 09/11] ibmvnic: Continue skb processing after skb completion error Nathan Fontenot
2017-04-29  8:16 ` [PATCH net-next 10/11] From: Thomas Falcon <tlfalcon@linux.vnet.ibm.com> Nathan Fontenot
2017-04-29  8:16 ` [PATCH net-next 11/11] ibmvnic: Move queue restart Nathan Fontenot
2017-04-29 17:18   ` kbuild test robot

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=20170429080710.13438.39798.stgit@ltcalpine2-lp23.aus.stglabs.ibm.com \
    --to=nfont@linux.vnet.ibm.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=jallen@linux.vnet.ibm.com \
    --cc=muvic@linux.vnet.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=tlfalcon@linux.vnet.ibm.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