Netdev List
 help / color / mirror / Atom feed
From: Juliet Kim <julietk@linux.vnet.ibm.com>
To: netdev@vger.kernel.org
Cc: tlfalcon@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 0/2] net/ibmvnic: serialization fixes
Date: Tue, 17 Sep 2019 18:19:02 -0500	[thread overview]
Message-ID: <c554bd78-2229-3c1c-3e12-071ad99ebcbb@linux.vnet.ibm.com> (raw)
In-Reply-To: <20190917145249.15334-1-julietk@linux.vnet.ibm.com>

I sent v3.  Please disregard v2.

On 9/17/19 9:52 AM, Juliet Kim wrote:
> This series includes two fixes. The first improves reset code to allow 
> linkwatch_event to proceed during reset. The second ensures that no more
> than one thread runs in reset at a time. 
>
> v2: 
> - Separate change param reset from do_reset()
> - Return IBMVNIC_OPEN_FAILED if __ibmvnic_open fails 
> - Remove setting wait_for_reset to false from __ibmvnic_reset(), this 
>   is done in wait_for_reset()
> - Move the check for force_reset_recovery from patch 1 to patch 2
>
> Juliet Kim (2):
>   net/ibmvnic: unlock rtnl_lock in reset so linkwatch_event can run
>   net/ibmvnic: prevent more than one thread from running in reset
>
>  drivers/net/ethernet/ibm/ibmvnic.c | 244 ++++++++++++++++++++++++++-----------
>  drivers/net/ethernet/ibm/ibmvnic.h |   4 +
>  2 files changed, 180 insertions(+), 68 deletions(-)
>

      parent reply	other threads:[~2019-09-17 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 14:52 [PATCH v2 0/2] net/ibmvnic: serialization fixes Juliet Kim
2019-09-17 14:52 ` [PATCH v2 1/2] net/ibmvnic: unlock rtnl_lock in reset so linkwatch_event can run Juliet Kim
2019-09-17 14:52 ` [PATCH v2 2/2] net/ibmvnic: prevent more than one thread from running in reset Juliet Kim
2019-09-17 23:19 ` Juliet Kim [this message]

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=c554bd78-2229-3c1c-3e12-071ad99ebcbb@linux.vnet.ibm.com \
    --to=julietk@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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