netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gwshan@linux.vnet.ibm.com
Cc: netdev@vger.kernel.org, joel@jms.id.au
Subject: Re: [PATCH v2 net 0/4] net/ncsi: More bug fixes
Date: Thu, 20 Oct 2016 11:23:25 -0400 (EDT)	[thread overview]
Message-ID: <20161020.112325.907295254918060127.davem@davemloft.net> (raw)
In-Reply-To: <1476924352-31165-1-git-send-email-gwshan@linux.vnet.ibm.com>

From: Gavin Shan <gwshan@linux.vnet.ibm.com>
Date: Thu, 20 Oct 2016 11:45:48 +1100

> This series fixes 2 issues that were found during NCSI's availability
> testing on BCM5718 and improves HNCDSC AEN handler:
> 
>    * PATCH[1] refactors the code so that minimal code change is put
>      to PATCH[2].
>    * PATCH[2] fixes the NCSI channel's stale link state before doing
>      failover.
>    * PATCH[3] chooses the hot channel, which was ever chosen as active
>      channel, when the available channels are all in link-down state.
>    * PATCH[4] improves Host Network Controller Driver Status Change
>      (HNCDSC) AEN handler
> 
> Changelog
> =========
> v2:
>    * Merged PATCH[v1 1/2] to PATCH[v2 1].
>    * Avoid if/else statements in ncsi_suspend_channel() as Joel suggested.
>    * Added comments to explain why we need retrieve last link states in
>      ncsi_suspend_channel().

Series applied, thanks.

      parent reply	other threads:[~2016-10-20 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20  0:45 [PATCH v2 net 0/4] net/ncsi: More bug fixes Gavin Shan
2016-10-20  0:45 ` [PATCH v2 net 1/4] net/ncsi: Avoid if statements in ncsi_suspend_channel() Gavin Shan
2016-10-20  0:45 ` [PATCH v2 net 2/4] net/ncsi: Fix stale link state of inactive channels on failover Gavin Shan
2016-10-20  0:45 ` [PATCH v2 net 3/4] net/ncsi: Choose hot channel as active one if necessary Gavin Shan
2016-10-20  0:45 ` [PATCH v2 net 4/4] net/ncsi: Improve HNCDSC AEN handler Gavin Shan
2016-10-20 15:23 ` 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=20161020.112325.907295254918060127.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=joel@jms.id.au \
    --cc=netdev@vger.kernel.org \
    /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).