From: Soumyadeep Hore <soumyadeep.hore@intel.com>
To: bruce.richardson@intel.com, aman.deep.singh@intel.com
Cc: dev@dpdk.org
Subject: [PATCH v2 0/2] Avoid rule duplication in CPFL PMD
Date: Fri, 5 Jul 2024 05:08:29 +0000 [thread overview]
Message-ID: <20240705050831.2639342-1-soumyadeep.hore@intel.com> (raw)
In-Reply-To: <20240704051835.2630052-1-soumyadeep.hore@intel.com>
This patchset avoids flow rule duplication which was possible
previously in CPFL PMD.
---
v2:
* Addressed review comments
* Added Fixes tags
* Fixed CI warnings
---
Soumyadeep Hore (2):
net/cpfl: fix check for opcodes of received ctlq messages
net/cpfl: fix +ve error codes for received ctlq messages
drivers/net/cpfl/cpfl_flow_engine_fxp.c | 2 +-
drivers/net/cpfl/cpfl_fxp_rule.c | 52 +++++++++++++++++++++++++
2 files changed, 53 insertions(+), 1 deletion(-)
--
2.43.0
next prev parent reply other threads:[~2024-07-05 5:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 5:18 [PATCH v1] net/cpfl: add checks for received ctlq messages Soumyadeep Hore
2024-07-04 12:49 ` Bruce Richardson
2024-07-05 5:08 ` Soumyadeep Hore [this message]
2024-07-05 5:08 ` [PATCH v2 1/2] net/cpfl: fix check for opcodes of " Soumyadeep Hore
2024-07-05 5:08 ` [PATCH v2 2/2] net/cpfl: fix +ve error codes for " Soumyadeep Hore
2024-07-05 8:30 ` [PATCH v3 0/2] Avoid rule duplication in CPFL PMD Soumyadeep Hore
2024-07-05 8:30 ` [PATCH v3 1/2] net/cpfl: fix check for opcodes of received ctlq messages Soumyadeep Hore
2024-07-05 9:49 ` Bruce Richardson
2024-07-05 8:30 ` [PATCH v3 2/2] net/cpfl: fix +ve error codes for " Soumyadeep Hore
2024-07-05 13:05 ` [PATCH v4 0/2] Avoid rule duplication in CPFL PMD Soumyadeep Hore
2024-07-05 13:05 ` [PATCH v4 1/2] net/cpfl: fix check for opcodes of received ctlq messages Soumyadeep Hore
2024-07-05 14:21 ` Bruce Richardson
2024-07-05 13:05 ` [PATCH v4 2/2] net/cpfl: fix +ve error codes for " Soumyadeep Hore
2024-07-05 14:47 ` [PATCH v4 0/2] Avoid rule duplication in CPFL PMD Bruce Richardson
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=20240705050831.2639342-1-soumyadeep.hore@intel.com \
--to=soumyadeep.hore@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).