linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: julietk@linux.vnet.ibm.com
Cc: netdev@vger.kernel.org, tlfalcon@linux.vnet.ibm.com,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v4 0/2] net/ibmvnic: serialization fixes
Date: Wed, 25 Sep 2019 13:41:59 +0200 (CEST)	[thread overview]
Message-ID: <20190925.134159.1914660952439794832.davem@davemloft.net> (raw)
In-Reply-To: <20190920201123.18913-1-julietk@linux.vnet.ibm.com>

From: Juliet Kim <julietk@linux.vnet.ibm.com>
Date: Fri, 20 Sep 2019 16:11:21 -0400

> 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
> 
> v3:
> - Restore reset’s successful return in open failure case
> 
> v4:
> - Change resetting flag access to atomic

Series applied, thank you.

      parent reply	other threads:[~2019-09-25 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 20:11 [PATCH v4 0/2] net/ibmvnic: serialization fixes Juliet Kim
2019-09-20 20:11 ` [PATCH v4 1/2] net/ibmvnic: unlock rtnl_lock in reset so linkwatch_event can run Juliet Kim
2019-09-20 20:11 ` [PATCH v4 2/2] net/ibmvnic: prevent more than one thread from running in reset Juliet Kim
2019-09-25 11:41 ` David Miller [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=20190925.134159.1914660952439794832.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=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;
as well as URLs for NNTP newsgroup(s).