From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Guo, Jia" <jia.guo@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Xu <IMCEAINVALID-Xu@intel.com>,
"Xu, HailinX" <hailinx.xu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/iavf: fix invalid cmd after pf reset
Date: Fri, 11 Sep 2020 10:45:42 +0000 [thread overview]
Message-ID: <d23dee03ae564149ae36b597beb8a0b8@intel.com> (raw)
In-Reply-To: <20200911101848.111384-1-jia.guo@intel.com>
> -----Original Message-----
> From: Guo, Jia <jia.guo@intel.com>
> Sent: Friday, September 11, 2020 6:19 PM
> To: Wu, Jingjing <jingjing.wu@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>;
> Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; Guo, Jia <jia.guo@intel.com>; Xu; Xu, HailinX
> <hailinx.xu@intel.com>
> Subject: [PATCH v2] net/iavf: fix invalid cmd after pf reset
>
> If PF reset is finished but VF reset is pending, VF should no need to send any
> invalid cmd to PF. That would avoid mass unexpected behaviors affecting the
> robust.
>
> Fixes: 22b123a36d07 ("net/avf: initialize PMD")
> Fixes: 9e03acd726cf ("net/iavf: fix flow access")
>
> Signed-off-by: Jeff Guo <jia.guo@intel.com>
> Tested-by: Xu, HailinX <hailinx.xu@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2020-09-11 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 5:21 [dpdk-dev] [PATCH v1] net/iavf: fix invalid cmd after pf reset Jeff Guo
2020-09-11 9:45 ` Xu, HailinX
2020-09-11 10:18 ` [dpdk-dev] [PATCH v2] " Jeff Guo
2020-09-11 10:45 ` Zhang, Qi Z [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=d23dee03ae564149ae36b597beb8a0b8@intel.com \
--to=qi.z.zhang@intel.com \
--cc=IMCEAINVALID-Xu@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=hailinx.xu@intel.com \
--cc=jia.guo@intel.com \
--cc=jingjing.wu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.