From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <rmody@marvell.com>, Shahed Shaikh <shshaikh@marvell.com>
Cc: dev@dpdk.org, stable@dpdk.org,
Kevin Traynor <ktraynor@redhat.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH v3 1/4] net/bnx2x: fix build with gcc11
Date: Wed, 12 May 2021 14:04:26 +0100 [thread overview]
Message-ID: <8b1e39a8-3aaa-fb89-cf7a-3cc452140f6b@intel.com> (raw)
In-Reply-To: <20210511131435.1226820-1-ferruh.yigit@intel.com>
On 5/11/2021 2:14 PM, Ferruh Yigit wrote:
> Reproduced with '--buildtype=debugoptimized' config,
> compiler version: gcc (GCC) 12.0.0 20210509 (experimental)
>
> Build error:
> In file included from ../drivers/net/bnx2x/bnx2x_rxtx.c:8:
> ../drivers/net/bnx2x/bnx2x_rxtx.c: In function ‘bnx2x_upd_rx_prod_fast’:
> ../drivers/net/bnx2x/bnx2x.h:1528:35:
> warning: ‘rx_prods’ is used uninitialized [-Wuninitialized]
> #define REG_WR32(sc, offset, val) bnx2x_reg_write32(sc, (offset), val)
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ../drivers/net/bnx2x/bnx2x.h:1531:33:
> note: in expansion of macro ‘REG_WR32’
> 1531 | #define REG_WR(sc, offset, val) REG_WR32(sc, offset, val)
> | ^~~~~~~~
> ../drivers/net/bnx2x/bnx2x_rxtx.c:331:9:
> note: in expansion of macro ‘REG_WR’
> 331 | REG_WR(sc, fp->ustorm_rx_prods_offset, val[0]);
> | ^~~~~~
> ../drivers/net/bnx2x/bnx2x_rxtx.c:324:40: note: ‘rx_prods’ declared here
> 324 | struct ustorm_eth_rx_producers rx_prods = { 0 };
> | ^~~~~~~~
>
> REG_WR32 requires 'uint32_t', use union instead of cast to 'uint32_t'.
>
> Bugzilla ID: 692
> Fixes: 38dff79ba736 ("net/bnx2x: update HSI")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Acked-by: Kevin Traynor <ktraynor@redhat.com>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-05-12 13:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 15:03 [dpdk-dev] [PATCH 1/4] net/bnx2x: fix build with gcc11 Ferruh Yigit
2021-05-10 15:03 ` [dpdk-dev] [PATCH 2/4] " Ferruh Yigit
2021-05-10 15:03 ` [dpdk-dev] [PATCH 3/4] net/ice/base: " Ferruh Yigit
2021-05-10 17:04 ` Wang, Haiyue
2021-05-10 17:13 ` Wang, Haiyue
2021-05-10 17:31 ` Ferruh Yigit
2021-05-10 17:55 ` Stillwell Jr, Paul M
2021-05-10 17:28 ` Ferruh Yigit
2021-05-11 1:59 ` Wang, Haiyue
2021-05-11 9:33 ` Ferruh Yigit
2021-05-11 9:08 ` Kevin Traynor
2021-05-10 15:03 ` [dpdk-dev] [PATCH 4/4] net/tap: " Ferruh Yigit
2021-05-11 12:28 ` Kevin Traynor
2021-05-11 11:44 ` [dpdk-dev] [PATCH v2 1/4] net/bnx2x: " Ferruh Yigit
2021-05-11 11:44 ` [dpdk-dev] [PATCH v2 2/4] " Ferruh Yigit
2021-05-11 12:27 ` Kevin Traynor
2021-05-11 11:44 ` [dpdk-dev] [PATCH v2 3/4] net/ice/base: " Ferruh Yigit
2021-05-11 11:44 ` [dpdk-dev] [PATCH v2 4/4] net/tap: " Ferruh Yigit
2021-05-11 12:26 ` [dpdk-dev] [PATCH v2 1/4] net/bnx2x: " Kevin Traynor
2021-05-11 13:14 ` [dpdk-dev] [PATCH v3 " Ferruh Yigit
2021-05-11 13:14 ` [dpdk-dev] [PATCH v3 2/4] " Ferruh Yigit
2021-05-11 13:14 ` [dpdk-dev] [PATCH v3 3/4] net/ice/base: " Ferruh Yigit
2021-05-12 7:43 ` [dpdk-dev] [dpdk-stable] " Wang, Haiyue
2021-05-11 13:14 ` [dpdk-dev] [PATCH v3 4/4] net/tap: " Ferruh Yigit
2021-05-12 13:04 ` Ferruh Yigit [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=8b1e39a8-3aaa-fb89-cf7a-3cc452140f6b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=rmody@marvell.com \
--cc=shshaikh@marvell.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.