From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
"Nithin Kumar Dabilpuram" <ndabilpuram@marvell.com>,
Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
"Marko Kovacevic" <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/octeontx2: add gre key parsing support
Date: Sun, 28 Jul 2019 17:22:24 +0000 [thread overview]
Message-ID: <BYAPR18MB24246344D8690DC519AD69FFC8C20@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20190726090303.7809-1-kirankumark@marvell.com>
> -----Original Message-----
> From: kirankumark@marvell.com <kirankumark@marvell.com>
> Sent: Friday, July 26, 2019 2:33 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Nithin Kumar
> Dabilpuram <ndabilpuram@marvell.com>; Kiran Kumar Kokkilagadda
> <kirankumark@marvell.com>; John McNamara
> <john.mcnamara@intel.com>; Marko Kovacevic
> <marko.kovacevic@intel.com>
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] net/octeontx2: add gre key parsing support
>
> From: Kiran Kumar K <kirankumark@marvell.com>
>
> Adding support to parse GRE KEY for octeontx2 Flow.
> Matching on GRE Key will only work, if checksum and routing bits in the GRE
> header are equal to 0.
>
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
Instead of introducing a new colum for RTE_FLOW_ITEM_TYPE_GRE_KEY comment,
add the comment as NOTE
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-mrvl/master. Thanks
prev parent reply other threads:[~2019-07-28 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 9:03 kirankumark
2019-07-28 17:22 ` Jerin Jacob Kollanukkaran [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=BYAPR18MB24246344D8690DC519AD69FFC8C20@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=kirankumark@marvell.com \
--cc=marko.kovacevic@intel.com \
--cc=ndabilpuram@marvell.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).