From: Manish Kurup <manish.kurup@broadcom.com>
To: dev@dpdk.org
Cc: ajit.khaparde@broadcom.com
Subject: [PATCH v4 54/57] net/bnxt/tf_ulp: fixes to enable TF functionality
Date: Tue, 21 Oct 2025 15:01:55 -0400 [thread overview]
Message-ID: <20251021190158.74064-2-manish.kurup@broadcom.com> (raw)
In-Reply-To: <20251021190158.74064-1-manish.kurup@broadcom.com>
1. Fix RTE_ACTION last item
Signed-off-by: Manish Kurup <manish.kurup@broadcom.com>
Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
---
drivers/net/bnxt/tf_ulp/ulp_rte_parser.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/bnxt/tf_ulp/ulp_rte_parser.c b/drivers/net/bnxt/tf_ulp/ulp_rte_parser.c
index 82baf722cd..26823858b5 100644
--- a/drivers/net/bnxt/tf_ulp/ulp_rte_parser.c
+++ b/drivers/net/bnxt/tf_ulp/ulp_rte_parser.c
@@ -211,7 +211,7 @@ bnxt_ulp_rte_parser_act_parse(const struct rte_flow_action actions[],
hdr_info = &ulp_vendor_act_info[action_item->type -
BNXT_RTE_FLOW_ACTION_TYPE_END];
} else {
- if (action_item->type > RTE_FLOW_ACTION_TYPE_INDIRECT)
+ if (action_item->type > RTE_FLOW_ACTION_TYPE_REPRESENTED_PORT)
goto act_parser_error;
/* get the header information from the act info table */
hdr_info = &ulp_act_info[action_item->type];
--
2.39.5 (Apple Git-154)
next prev parent reply other threads:[~2025-10-21 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 19:01 [PATCH v4 53/57] net/bnxt/tf_core: fix truflow PF init failure on sriov disabled Manish Kurup
2025-10-21 19:01 ` Manish Kurup [this message]
2025-10-21 19:01 ` [PATCH v4 55/57] net/bnxt/tf_ulp: add feature bit rx miss handling Manish Kurup
2025-10-21 19:01 ` [PATCH v4 56/57] net/bnxt: add support for truflow promiscuous mode Manish Kurup
2025-10-21 19:01 ` [PATCH v4 57/57] net/bnxt/tf_ulp: remove Truflow DEBUG code Manish Kurup
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=20251021190158.74064-2-manish.kurup@broadcom.com \
--to=manish.kurup@broadcom.com \
--cc=ajit.khaparde@broadcom.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).