From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Rasesh Mody <rmody@marvell.com>,
GR-Linux-NIC-Dev@marvell.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH net v1 1/1] bnx2: Fix unused data compilation warning
Date: Fri, 28 Feb 2025 12:05:37 +0200 [thread overview]
Message-ID: <20250228100538.32029-1-andriy.shevchenko@linux.intel.com> (raw)
In some configuration, compilation raises warnings related to unused
data. Indeed, depending on configuration, those data can be unused.
Mark those data as __maybe_unused to avoid compilation warnings.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/net/ethernet/broadcom/bnx2.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/broadcom/bnx2.c b/drivers/net/ethernet/broadcom/bnx2.c
index 6ec773e61182..a40ef3ec38b3 100644
--- a/drivers/net/ethernet/broadcom/bnx2.c
+++ b/drivers/net/ethernet/broadcom/bnx2.c
@@ -2887,7 +2887,7 @@ bnx2_tx_int(struct bnx2 *bp, struct bnx2_napi *bnapi, int budget)
last = tx_buf->nr_frags;
for (i = 0; i < last; i++) {
- struct bnx2_sw_tx_bd *tx_buf;
+ struct bnx2_sw_tx_bd *tx_buf __maybe_unused;
sw_cons = BNX2_NEXT_TX_BD(sw_cons);
@@ -2994,7 +2994,7 @@ static inline void
bnx2_reuse_rx_data(struct bnx2 *bp, struct bnx2_rx_ring_info *rxr,
u8 *data, u16 cons, u16 prod)
{
- struct bnx2_sw_bd *cons_rx_buf, *prod_rx_buf;
+ struct bnx2_sw_bd *cons_rx_buf __maybe_unused, *prod_rx_buf;
struct bnx2_rx_bd *cons_bd, *prod_bd;
cons_rx_buf = &rxr->rx_buf_ring[cons];
--
2.47.2
next reply other threads:[~2025-02-28 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 10:05 Andy Shevchenko [this message]
2025-03-04 1:21 ` [PATCH net v1 1/1] bnx2: Fix unused data compilation warning Jakub Kicinski
2025-03-04 10:56 ` Andy Shevchenko
2025-03-04 11:39 ` Paolo Abeni
2025-03-04 11:58 ` Andy Shevchenko
2025-03-04 13:41 ` Andy Shevchenko
2025-03-04 16:35 ` Jakub Kicinski
2025-03-05 10:00 ` Andy Shevchenko
2025-03-11 12:51 ` Marek Szyprowski
2025-03-12 16:20 ` Andy Shevchenko
2025-04-14 10:08 ` Andy Shevchenko
2025-04-15 9:43 ` Andy Shevchenko
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=20250228100538.32029-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmody@marvell.com \
/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).