From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yang, MurphyX" <murphyx.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
"Guo, Jia" <jia.guo@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Yang, SteveX" <stevex.yang@intel.com>,
"Zhang, RobinX" <robinx.zhang@intel.com>,
"Yang, MurphyX" <murphyx.yang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: fix inappropriate config during flow validate
Date: Thu, 1 Apr 2021 11:54:39 +0000 [thread overview]
Message-ID: <dbc6afcffbcd488bb3774fbc04afb2de@intel.com> (raw)
In-Reply-To: <20210401032332.33368-1-murphyx.yang@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Murphy Yang
> Sent: Thursday, April 1, 2021 11:24 AM
> To: dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>; Guo, Jia <jia.guo@intel.com>;
> Xing, Beilei <beilei.xing@intel.com>; Yang, SteveX <stevex.yang@intel.com>;
> Zhang, RobinX <robinx.zhang@intel.com>; Yang, MurphyX
> <murphyx.yang@intel.com>
> Subject: [dpdk-dev] [PATCH v2] net/i40e: fix inappropriate config during flow
> validate
>
> The configuration of FDIR input set should not be set during flow validate. It
> should be set when flow create.
>
> Fixes: fe5d0e85b713 ("net/i40e: fix flow director flex configuration")
> Fixes: 15018d79f0be ("net/i40e: add FDIR support for GTP-C and GTP-U")
>
> Signed-off-by: Murphy Yang <murphyx.yang@intel.com>
Added ack in v1
Acked-by: Beilei Xing <Beilei.xing@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2021-04-01 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 2:44 [dpdk-dev] [PATCH] net/i40e: fix inappropriate config during flow validate Murphy Yang
2021-03-30 14:01 ` Xing, Beilei
2021-04-01 3:23 ` [dpdk-dev] [PATCH v2] " Murphy Yang
2021-04-01 11:54 ` 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=dbc6afcffbcd488bb3774fbc04afb2de@intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.com \
--cc=murphyx.yang@intel.com \
--cc=qiming.yang@intel.com \
--cc=robinx.zhang@intel.com \
--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 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.