From: Ratheesh Kannoth <rkannoth@marvell.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: RE: [EXT] linux-next: build failure after merge of the net-next tree
Date: Thu, 7 Jul 2022 04:56:44 +0000 [thread overview]
Message-ID: <MWHPR1801MB19186E4EB125181807ECDB5CD3839@MWHPR1801MB1918.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220707110015.3549e789@canb.auug.org.au>
-----Original Message-----
From: Stephen Rothwell <sfr@canb.auug.org.au>
Sent: Thursday, July 7, 2022 6:30 AM
To: David Miller <davem@davemloft.net>; Networking <netdev@vger.kernel.org>
Cc: Ratheesh Kannoth <rkannoth@marvell.com>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: [EXT] linux-next: build failure after merge of the net-next tree
External Email
----------------------------------------------------------------------
>Hi all,
>After merging the net-next tree, today's linux-next build (x86_64
>allmodconfig) failed like this:
>In file included from drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c:14:
>drivers/net/ethernet/marvell/octeontx2/af/npc_profile.h:15120:28: error: 'npc_mkex_default' defined but not used [-Werror=unused-variable]
>15120 | static struct npc_mcam_kex npc_mkex_default = {
> | ^~~~~~~~~~~~~~~~
>drivers/net/ethernet/marvell/octeontx2/af/npc_profile.h:15000:30: error: 'npc_lt_defaults' defined but not used [-Werror=unused-variable]
>15000 | static struct npc_lt_def_cfg npc_lt_defaults = {
| ^~~~~~~~~~~~~~~
>drivers/net/ethernet/marvell/octeontx2/af/npc_profile.h:14901:31: error: 'npc_kpu_profiles' defined but not used [-Werror=unused-variable]
>14901 | static struct npc_kpu_profile npc_kpu_profiles[] = {
| ^~~~~~~~~~~~~~~~
>drivers/net/ethernet/marvell/octeontx2/af/npc_profile.h:483:38: error: 'ikpu_action_entries' defined but not used [-Werror=unused-variable]
> 483 | static struct npc_kpu_profile_action ikpu_action_entries[] = {
> | ^~~~~~~~~~~~~~~~~~~
>cc1: all warnings being treated as errors
>Caused by commit
>c6238bc0614d ("octeontx2-af: Drop rules for NPC MCAM")
>I do wonder why static structs are declared in a header file ...
>I have used the net-next tree from next-20220706 for today.
I have fixed compilation errors and reposted V2 patch set. Apologies for the trouble.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2022-07-07 4:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 1:00 linux-next: build failure after merge of the net-next tree Stephen Rothwell
2022-07-07 4:56 ` Ratheesh Kannoth [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=MWHPR1801MB19186E4EB125181807ECDB5CD3839@MWHPR1801MB1918.namprd18.prod.outlook.com \
--to=rkannoth@marvell.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).