From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, zhoumin@loongson.cn, stable@dpdk.org,
Somnath Kotur <somnath.kotur@broadcom.com>,
Mike Baucom <michael.baucom@broadcom.com>,
Kishore Padmanabha <kishore.padmanabha@broadcom.com>,
Ferruh Yigit <ferruh.yigit@xilinx.com>
Subject: Re: [PATCH] net/bnxt: fix build with GCC 13
Date: Mon, 3 Oct 2022 21:01:23 -0700 [thread overview]
Message-ID: <CACZ4nhu7y=nHYdWafOZe2UcXWT5KpZmQYom5x0ca5oCsR2KpYQ@mail.gmail.com> (raw)
In-Reply-To: <20221003165744.117581-1-david.marchand@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
On Mon, Oct 3, 2022 at 9:58 AM David Marchand <david.marchand@redhat.com> wrote:
>
> 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>
Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Patch applied to dpdk-next-net-brcm.
Thanks
Ajit
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
prev parent reply other threads:[~2022-10-04 4:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 16:57 David Marchand
2022-10-04 4:01 ` Ajit Khaparde [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='CACZ4nhu7y=nHYdWafOZe2UcXWT5KpZmQYom5x0ca5oCsR2KpYQ@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--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).