From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qi Zhang <qi.z.zhang@intel.com>,
jingjing.wu@intel.com, helin.zhang@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2] net/i40e: fix VF link status update
Date: Thu, 13 Apr 2017 11:54:59 +0100 [thread overview]
Message-ID: <fc5b79c1-1d69-ad18-bd80-c453d85dcf86@intel.com> (raw)
In-Reply-To: <1492025400-8724-1-git-send-email-qi.z.zhang@intel.com>
On 4/12/2017 8:30 PM, Qi Zhang wrote:
> VF link status rely on PF's notification, so when PF link status
> be updated, it should notify VF to update link status also.
> Current implementation only cover part of the situation when PF's link
> status is updated, call i40e_notify_all_vfs_link_status in
> i4e_dev_link_update will cover all situationa.
>
> Fixes: bb6722fb5c0e ("net/i40e: fix VF bonded device link down")
> Cc: stable@dpdk.org
>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-04-13 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1491983762-35619-1-git-send-email-qi.z.zhang@intel.com>
2017-04-12 19:30 ` Qi Zhang
2017-04-13 10:54 ` 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=fc5b79c1-1d69-ad18-bd80-c453d85dcf86@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.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).