From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ray Kinsella <mdr@ashroe.eu>, Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Satheesh Paul <psatheesh@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] drivers: enable keep flow rule device capability for cnxk
Date: Fri, 18 Feb 2022 11:37:36 +0530 [thread overview]
Message-ID: <CALBAE1Ppcgu6cGFK3cBFfnqS1mR4YgaWvm84YpOQyRWfyUbnhw@mail.gmail.com> (raw)
In-Reply-To: <87bkz9iwue.fsf@mdr78.vserver.site>
On Mon, Feb 14, 2022 at 3:39 PM Ray Kinsella <mdr@ashroe.eu> wrote:
>
>
> psatheesh@marvell.com writes:
>
> > From: Kiran Kumar K <kirankumark@marvell.com>
> >
> > Adding changes to enable keep flow rule device capability.
> > With this change, flow rules will be kept across device restart.
> >
> > Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
> > Reviewed-by: Satheesh Paul <psatheesh@marvell.com>
> > ---
> > v2:
> > * Allow creating flow rule before device start.
> >
> > drivers/common/cnxk/roc_npc.c | 8 ++++++++
> > drivers/common/cnxk/roc_npc.h | 2 ++
> > drivers/common/cnxk/roc_npc_mcam.c | 20 ++++++++++++++++++++
> > drivers/common/cnxk/roc_npc_priv.h | 1 +
> > drivers/common/cnxk/version.map | 1 +
> > drivers/net/cnxk/cnxk_ethdev.c | 15 +++++++++++++--
> > drivers/net/cnxk/cnxk_ethdev_ops.c | 4 ++--
> > 7 files changed, 47 insertions(+), 4 deletions(-)
> >
>
> Acked-by: Ray Kinsella <mdr@ashroe.eu>
Applied to dpdk-next-net-mrvl/for-next-net. Thanks
>
> --
> Regards, Ray K
next prev parent reply other threads:[~2022-02-18 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 4:19 [dpdk-dev] [PATCH] " psatheesh
2022-01-25 9:50 ` Ray Kinsella
2022-02-14 4:33 ` [dpdk-dev] [PATCH v2] " psatheesh
2022-02-14 10:08 ` Ray Kinsella
2022-02-18 6:07 ` Jerin Jacob [this message]
2022-02-14 4:29 psatheesh
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=CALBAE1Ppcgu6cGFK3cBFfnqS1mR4YgaWvm84YpOQyRWfyUbnhw@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kirankumark@marvell.com \
--cc=mdr@ashroe.eu \
--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).