From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Wu, Wenjun1" <wenjun1.wu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/4] support AVF RSS and FDIR for GRE tunnel packet
Date: Tue, 6 Jul 2021 23:38:14 +0000 [thread overview]
Message-ID: <8f6b7d2d71ec45188a779b487e36f473@intel.com> (raw)
In-Reply-To: <4620181.dK3K1iW6DV@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, July 7, 2021 4:00 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: Wu, Wenjun1 <wenjun1.wu@intel.com>; dev@dpdk.org; Wu, Jingjing
> <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Yigit, Ferruh
> <ferruh.yigit@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v2 0/4] support AVF RSS and FDIR for GRE
> tunnel packet
>
> 21/06/2021 04:54, Zhang, Qi Z:
> > Acked-by: Qi Zhang <qi.z.zhang@intel.com>
> >
> > Applied to dpdk-next-net-intel.
>
> GRE should have been added to the new flow features table in
> doc/guides/nics/features/iavf.ini
>
> Will fix when pulling.
>
> For future pulls, please run devtools/check-doc-vs-code.sh
Thanks!
>
prev parent reply other threads:[~2021-07-06 23:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210527074845.1263679>
2021-06-02 2:24 ` Wenjun Wu
2021-06-02 2:24 ` [dpdk-dev] [PATCH v2 1/4] net/iavf: support flow pattern for GRE Wenjun Wu
2021-06-02 2:24 ` [dpdk-dev] [PATCH v2 2/4] common/iavf: add header types " Wenjun Wu
2021-06-02 2:24 ` [dpdk-dev] [PATCH v2 3/4] net/iavf: support AVF RSS for GRE tunnel packet Wenjun Wu
2021-06-02 2:24 ` [dpdk-dev] [PATCH v2 4/4] net/iavf: support AVF FDIR " Wenjun Wu
2021-06-10 16:18 ` Singh, Aman Deep
2021-06-21 2:54 ` [dpdk-dev] [PATCH v2 0/4] support AVF RSS and " Zhang, Qi Z
2021-07-06 20:00 ` Thomas Monjalon
2021-07-06 23:38 ` 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=8f6b7d2d71ec45188a779b487e36f473@intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@intel.com \
--cc=thomas@monjalon.net \
--cc=wenjun1.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 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).