From: Jerin Jacob <jerinjacobk@gmail.com>
To: psatheesh@marvell.com
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
dev@dpdk.org, Jerin Jacob <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] common/cnxk: add IPv6 routing ext flow type for cnxk
Date: Tue, 8 Aug 2023 19:22:06 +0530 [thread overview]
Message-ID: <CALBAE1N8r=E7v6Kdi0YKGH13PqXtnLUTHyzXOiF4g1iTsBKArA@mail.gmail.com> (raw)
In-Reply-To: <20230703051026.1843262-1-psatheesh@marvell.com>
On Mon, Jul 3, 2023 at 10:40 AM <psatheesh@marvell.com> wrote:
>
> From: Kiran Kumar K <kirankumark@marvell.com>
>
> Adding support to parse IPV6 routing ext flow type for cnxk.
>
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
> Reviewed-by: Satheesh Paul <psatheesh@marvell.com>
> Tested-by: Jerin Jacob <jerinj@marvell.com>
Updated the git commit as follows and applied to
dpdk-next-net-mrvl/for-next-net. Thanks
Author: Satheesh Paul <psatheesh@marvell.com>
Date: Mon Jul 3 10:40:26 2023 +0530
net/cnxk: support IPv6 routing ext flow type
Support to parse RTE_FLOW_ITEM_TYPE_IPV6_ROUTING_EXT rte_flow
type for cnxk device.
Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
commit 830d75fd19d9508237b69c66ffc0711671345f32
Author: Kiran Kumar K <kirankumark@marvell.com>
Date: Mon Jul 3 10:40:25 2023 +0530
common/cnxk: support IPv6 routing ext flow type
Support to parse IPV6 routing ext flow type.
Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
Reviewed-by: Satheesh Paul <psatheesh@marvell.com>
prev parent reply other threads:[~2023-08-08 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 5:10 psatheesh
2023-07-03 5:10 ` [dpdk-dev] [PATCH 2/2] net/cnxk: adding " psatheesh
2023-08-08 13:52 ` Jerin Jacob [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='CALBAE1N8r=E7v6Kdi0YKGH13PqXtnLUTHyzXOiF4g1iTsBKArA@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@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).