DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/sfc: fix missing notification on link status change
Date: Fri, 13 Sep 2019 18:52:56 +0100	[thread overview]
Message-ID: <8388aa5e-332c-3843-f8e0-810395385588@intel.com> (raw)
In-Reply-To: <1567766989-25918-1-git-send-email-arybchenko@solarflare.com>

On 9/6/2019 11:49 AM, Andrew Rybchenko wrote:
> rte_eth_linkstatus_set() returns 0 when link up status changes.
> 
> Fixes: 4abe903e5078 ("net/sfc: use link status helper functions")
> Cc: stable@dpdk.org
> 
> Reported-by: Shuki Katzenelson <shuki@lightbitslabs.com>
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2019-09-13 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 10:49 [dpdk-dev] " Andrew Rybchenko
2019-09-13 17:52 ` Ferruh Yigit [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=8388aa5e-332c-3843-f8e0-810395385588@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.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).