DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Liu, Lingyu" <lingyu.liu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"Guo, Junfeng" <junfeng.guo@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] Support outer layer FDIR for GTPoGRE packet
Date: Tue, 6 Jul 2021 23:27:43 +0000	[thread overview]
Message-ID: <ee87670b185a463eb246d2e804f544aa@intel.com> (raw)
In-Reply-To: <232231914.2rZhWiTFky@thomas>



> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, July 7, 2021 6:11 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: Liu, Lingyu <lingyu.liu@intel.com>; dev@dpdk.org; Xing, Beilei
> <beilei.xing@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>; Guo,
> Junfeng <junfeng.guo@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v2 0/3] Support outer layer FDIR for
> GTPoGRE packet
> 
> 06/07/2021 04:40, Zhang, Qi Z:
> > From: Liu, Lingyu <lingyu.liu@intel.com>
> > > Add support for outer most L3 layer FDIR for GTPoGRE packet. GTPU
> > > TEID FDIR is supported for GTPoGRE flow pattern without inner L3,L4
> > > fields. GTPU enhance header is supported.
> > >
> > > Lingyu Liu (3):
> > >   net/iavf: add flow pattern for GTPoGRE
> > >   net/iavf: add AVF FDIR for GTPoGRE tunnel packet
> > >   doc: release note for GTPoGRE FDIR
> >
> > Acked-by: Qi Zhang <qi.z.zhang@intel.com>
> >
> > Applied to dpdk-next-net-intel.
> 
> The difference with the series "support AVF RSS and FDIR for GTPoGRE
> packet"
> is not reflected in titles.
> I prefer not pulling these 2 series so you can rework the titles and release
> notes in dpdk-next-net-intel.
> Note: the release notes should be updated in each patch, not separately.
> 

OK, I think we can merge 2 series into one as well as the following fix.

  reply	other threads:[~2021-07-06 23:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06  7:42 Lingyu Liu
2021-07-06  2:40 ` Zhang, Qi Z
2021-07-06 22:10   ` Thomas Monjalon
2021-07-06 23:27     ` Zhang, Qi Z [this message]
2021-07-06  7:42 ` [dpdk-dev] [PATCH v2 1/3] net/iavf: add flow pattern for GTPoGRE Lingyu Liu
2021-07-06  7:42 ` [dpdk-dev] [PATCH v2 2/3] net/iavf: add AVF FDIR for GTPoGRE tunnel packet Lingyu Liu
2021-07-06  7:42 ` [dpdk-dev] [PATCH v2 3/3] doc: release note for GTPoGRE FDIR Lingyu Liu
2021-07-07 12:57 ` [dpdk-dev] [PATCH v1 0/4] support AVF RSS and FDIR for GTPoGRE packet Lingyu Liu
2021-07-07  7:25   ` Zhang, Qi Z
2021-07-07 12:57   ` [dpdk-dev] [PATCH v1 1/4] net/iavf: support flow pattern for GTPoGRE Lingyu Liu
2021-07-07 12:57   ` [dpdk-dev] [PATCH v1 2/4] net/iavf: support AVF FDIR for GTPoGRE tunnel packet Lingyu Liu
2021-07-07 12:57   ` [dpdk-dev] [PATCH v1 3/4] net/iavf: support AVF RSS for GTPoGRE packet Lingyu Liu
2021-07-07 12:57   ` [dpdk-dev] [PATCH v1 4/4] doc: update iavf driver FDIR/RSS for GTPoGRE Lingyu Liu
2021-07-09  8:59     ` Thomas Monjalon
2021-07-12  0:24       ` Zhang, Qi Z

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=ee87670b185a463eb246d2e804f544aa@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=junfeng.guo@intel.com \
    --cc=lingyu.liu@intel.com \
    --cc=thomas@monjalon.net \
    /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).