From: Kevin Traynor <ktraynor@redhat.com>
To: Steve Yang <stevex.yang@intel.com>, stable@dpdk.org
Cc: beilei.xing@intel.com, jia.guo@intel.com,
Guinan Sun <guinanx.sun@intel.com>
Subject: Re: [dpdk-stable] [DPDK 18.11] net/i40e: fix link status
Date: Fri, 11 Dec 2020 09:46:47 +0000 [thread overview]
Message-ID: <240bcaea-50b0-ddd8-243d-174d2708b5a8@redhat.com> (raw)
In-Reply-To: <20201211090105.28432-3-stevex.yang@intel.com>
On 11/12/2020 09:01, Steve Yang wrote:
> From: Guinan Sun <guinanx.sun@intel.com>
>
> [ upstream commit 3db12449e119587648adf0b189c0e45502b71285 ]
>
> If the PF driver supports the new speed reporting capabilities
> then use link_event_adv instead of link_event to get the speed.
>
> Fixes: 2a73125b7041 ("i40evf: fix link info update")
> Cc: stable@dpdk.org
>
> Acked-by: Jeff Guo <jia.guo@intel.com>
> Tested-by: Jiaqi Min <jiaqix.min@intel.com>
>
> Signed-off-by: Guinan Sun <guinanx.sun@intel.com>
> ---
> drivers/net/i40e/base/virtchnl.h | 16 ++++++++++++-
> drivers/net/i40e/i40e_ethdev_vf.c | 38 ++++++++++++++++++++++++++++---
> 2 files changed, 50 insertions(+), 4 deletions(-)
Applied, thanks.
next prev parent reply other threads:[~2020-12-11 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 9:01 [dpdk-stable] [DPDK 18.11] net/i40e: fix filter pctype Steve Yang
2020-12-11 9:01 ` [dpdk-stable] [DPDK 18.11] net/i40e: fix flow director initialisation Steve Yang
2020-12-11 9:46 ` Kevin Traynor
2020-12-11 9:01 ` [dpdk-stable] [DPDK 18.11] net/i40e: fix link status Steve Yang
2020-12-11 9:46 ` Kevin Traynor [this message]
2020-12-11 9:01 ` [dpdk-stable] [DPDK 18.11] net/i40e: fix queue region in RSS flow Steve Yang
2020-12-11 9:44 ` Kevin Traynor
2020-12-11 9:01 ` [dpdk-stable] [DPDK 18.11] net/i40e: fix recreating flexible flow director rule Steve Yang
2020-12-11 9:47 ` Kevin Traynor
2020-12-11 9:46 ` [dpdk-stable] [DPDK 18.11] net/i40e: fix filter pctype Kevin Traynor
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=240bcaea-50b0-ddd8-243d-174d2708b5a8@redhat.com \
--to=ktraynor@redhat.com \
--cc=beilei.xing@intel.com \
--cc=guinanx.sun@intel.com \
--cc=jia.guo@intel.com \
--cc=stable@dpdk.org \
--cc=stevex.yang@intel.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).