From: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
To: netdev@vger.kernel.org
Cc: nfont@linux.vnet.ibm.com, jallen@linux.vnet.ibm.com
Subject: Re: [PATCH 0/3] ibmvnic: Clean up net close and fix reset bug
Date: Wed, 7 Mar 2018 17:43:06 -0600 [thread overview]
Message-ID: <51a99f7d-13df-7922-0f46-8ea9afccfb3c@linux.vnet.ibm.com> (raw)
In-Reply-To: <1520466072-17377-1-git-send-email-tlfalcon@linux.vnet.ibm.com>
On 03/07/2018 05:41 PM, Thomas Falcon wrote:
> This patch set cleans up and reorganizes the driver's net_device
> close function and leverages that to fix up a bug that can occur
> during some device resets. Some reset cases require the backing
> adapter to be disabled before continuing, but other cases, such as
> during a device failover or partition migration, do not require this
> step. Since the device will not be initialized at this stage and
> its command-processing queue is closed, do not send the request to
> disable the device as it could result in an error or timeout
> disrupting the reset.
>
> Thomas Falcon (3):
> ibmvnic: Clean up device close
> ibmvnic: Reorganize device close
> ibmvnic: Do not disable device during failover or partition migration
>
> drivers/net/ethernet/ibm/ibmvnic.c | 48 ++++++++++++++++++--------------------
> 1 file changed, 23 insertions(+), 25 deletions(-)
>
Crud, this series is meant for the net-next tree, but I forgot to include it in the patch tag.
next prev parent reply other threads:[~2018-03-07 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 23:41 [PATCH 0/3] ibmvnic: Clean up net close and fix reset bug Thomas Falcon
2018-03-07 23:41 ` [PATCH 1/3] ibmvnic: Clean up device close Thomas Falcon
2018-03-07 23:41 ` [PATCH 2/3] ibmvnic: Reorganize " Thomas Falcon
2018-03-07 23:41 ` [PATCH 3/3] ibmvnic: Do not disable device during failover or partition migration Thomas Falcon
2018-03-07 23:43 ` Thomas Falcon [this message]
2018-03-08 1:24 ` [PATCH 0/3] ibmvnic: Clean up net close and fix reset bug 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=51a99f7d-13df-7922-0f46-8ea9afccfb3c@linux.vnet.ibm.com \
--to=tlfalcon@linux.vnet.ibm.com \
--cc=jallen@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nfont@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;
as well as URLs for NNTP newsgroup(s).