From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/octeontx2: add ipv6 ext parsing support
Date: Mon, 22 Jul 2019 08:08:08 +0000 [thread overview]
Message-ID: <BYAPR18MB242482E632444BAF7103DF96C8C40@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20190719031841.10526-1-kirankumark@marvell.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of
> kirankumark@marvell.com
> Sent: Friday, July 19, 2019 8:49 AM
> To: dev@dpdk.org
> Cc: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
> Subject: [dpdk-dev] [PATCH] net/octeontx2: add ipv6 ext parsing support
>
> From: Kiran Kumar K <kirankumark@marvell.com>
>
> Adding support for ipv6_ext header parsing in the octeontx2 flow.
>
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-mrvl/master. Thanks
prev parent reply other threads:[~2019-07-22 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 3:18 kirankumark
2019-07-22 8:08 ` 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=BYAPR18MB242482E632444BAF7103DF96C8C40@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kirankumark@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).