From: "Arnd Bergmann" <arnd@arndb.de>
To: "Arnd Bergmann" <arnd@kernel.org>,
"Sunil Goutham" <sgoutham@marvell.com>,
"Geetha sowjanya" <gakula@marvell.com>,
"Subbaraya Sundeep Bhatta" <sbhatta@marvell.com>,
hariprasad <hkelam@marvell.com>,
"Bharat Bhushan" <bbhushan2@marvell.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>
Cc: "David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Suman Ghosh" <sumang@marvell.com>,
"Sai Krishna Gajula" <saikrishnag@marvell.com>,
"Nithin Dabilpuram" <ndabilpuram@marvell.com>,
Netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] octeontx2: hide unused label
Date: Wed, 19 Feb 2025 17:03:49 +0100 [thread overview]
Message-ID: <b7462eca-4900-4fb6-8ddc-7d27897ced7f@app.fastmail.com> (raw)
In-Reply-To: <20250219142433.63312-1-arnd@kernel.org>
On Wed, Feb 19, 2025, at 15:24, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> A previous patch introduces a build-time warning when CONFIG_DCB
> is disabled:
>
> drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c: In function
> 'otx2_probe':
> drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c:3217:1: error:
> label 'err_free_zc_bmap' defined but not used [-Werror=unused-label]
> drivers/net/ethernet/marvell/octeontx2/nic/otx2_vf.c: In function
> 'otx2vf_probe':
> drivers/net/ethernet/marvell/octeontx2/nic/otx2_vf.c:740:1: error:
> label 'err_free_zc_bmap' defined but not used [-Werror=unused-label]
>
> Add the same #ifdef check around it.
>
> Fixes: efabce290151 ("octeontx2-pf: AF_XDP zero copy receive support")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Sorry, this version caused a different build failure a few randconfig
builds in, please ignore and wait for v2.
Arnd
prev parent reply other threads:[~2025-02-19 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 14:24 Arnd Bergmann
2025-02-19 16:03 ` Arnd Bergmann [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=b7462eca-4900-4fb6-8ddc-7d27897ced7f@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@kernel.org \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndabilpuram@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saikrishnag@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sumang@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
all inboxes | Powered by JetHome®