From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <rasesh.mody@cavium.com>, dev@dpdk.org
Cc: Shahed Shaikh <shahed.shaikh@cavium.com>,
Dept-EngDPDKDev@cavium.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 1/2] net/qede: fix incorrect link status update
Date: Fri, 8 Jun 2018 19:42:20 +0100 [thread overview]
Message-ID: <53cf37b4-af02-a56f-2069-421f3c8a97cf@intel.com> (raw)
In-Reply-To: <1528389052-4875-1-git-send-email-rasesh.mody@cavium.com>
On 6/7/2018 5:30 PM, Rasesh Mody wrote:
> From: Shahed Shaikh <shahed.shaikh@cavium.com>
>
> qede_link_update() always returns -1 i.e. link not changed,
> becasue it compares the variables which always hold same value.
>
> Fix this function by using rte_eth_linkstatus_set().
>
> Fixes: 2ea6f76aff40 ("qede: add core driver")
> Cc: stable@dpdk.org
>
> Signed-off-by: Shahed Shaikh <shahed.shaikh@cavium.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-06-08 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 16:30 Rasesh Mody
2018-06-07 16:30 ` [dpdk-stable] [PATCH 2/2] net/qede: fix link change event notification Rasesh Mody
2018-06-08 18:42 ` 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=53cf37b4-af02-a56f-2069-421f3c8a97cf@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=dev@dpdk.org \
--cc=rasesh.mody@cavium.com \
--cc=shahed.shaikh@cavium.com \
--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).