From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: zhoumin@loongson.cn, stable@dpdk.org,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Mike Baucom <michael.baucom@broadcom.com>,
Kishore Padmanabha <kishore.padmanabha@broadcom.com>
Subject: [PATCH] net/bnxt: fix build with GCC 13
Date: Mon, 3 Oct 2022 18:57:44 +0200 [thread overview]
Message-ID: <20221003165744.117581-1-david.marchand@redhat.com> (raw)
GCC 13 complains with:
../../../dpdk/drivers/net/bnxt/tf_ulp/ulp_flow_db.c:962:1:
error: conflicting types for ‘ulp_flow_db_flush_flows’ due to
enum/integer mismatch; have ‘int32_t(struct bnxt_ulp_context *,
enum bnxt_ulp_fdb_type)’ {aka ‘int(struct bnxt_ulp_context *,
enum bnxt_ulp_fdb_type)’} [-Werror=enum-int-mismatch]
962 | ulp_flow_db_flush_flows(struct bnxt_ulp_context *ulp_ctx,
| ^~~~~~~~~~~~~~~~~~~~~~~
In file included from
../../../dpdk/drivers/net/bnxt/tf_ulp/ulp_flow_db.c:12:
../../../dpdk/drivers/net/bnxt/tf_ulp/ulp_flow_db.h:211:1: note:
previous declaration of ‘ulp_flow_db_flush_flows’ with type
‘int32_t(struct bnxt_ulp_context *, uint32_t)’ {aka ‘int(struct
bnxt_ulp_context *, unsigned int)’}
211 | ulp_flow_db_flush_flows(struct bnxt_ulp_context *ulp_ctx,
| ^~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
Fixes: 30683082a8ed ("net/bnxt: combine default and regular flows")
Cc: stable@dpdk.org
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
drivers/net/bnxt/tf_ulp/ulp_flow_db.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/bnxt/tf_ulp/ulp_flow_db.h b/drivers/net/bnxt/tf_ulp/ulp_flow_db.h
index b27678dae9..2b02836a40 100644
--- a/drivers/net/bnxt/tf_ulp/ulp_flow_db.h
+++ b/drivers/net/bnxt/tf_ulp/ulp_flow_db.h
@@ -203,13 +203,13 @@ ulp_flow_db_resource_get(struct bnxt_ulp_context *ulp_ctxt,
* Flush all flows in the flow database.
*
* ulp_ctxt [in] Ptr to ulp context
- * tbl_idx [in] The index to table
+ * flow_type [in] - specify default or regular
*
* returns 0 on success or negative number on failure
*/
int32_t
ulp_flow_db_flush_flows(struct bnxt_ulp_context *ulp_ctx,
- uint32_t idx);
+ enum bnxt_ulp_fdb_type flow_type);
/*
* Flush all flows in the flow database that belong to a device function.
--
2.37.3
next reply other threads:[~2022-10-03 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 16:57 David Marchand [this message]
2022-10-04 4:01 ` Ajit Khaparde
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=20221003165744.117581-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=kishore.padmanabha@broadcom.com \
--cc=michael.baucom@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=stable@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).