From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: kernel test robot <lkp@intel.com>, Jakub Kicinski <kuba@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [arm:zii 20/80] drivers/net/dsa/xrs700x/xrs700x.c:714:37: warning: 'xrs700x_phylink_mac_ops' defined but not used
Date: Thu, 18 Apr 2024 09:20:42 +0100 [thread overview]
Message-ID: <ZiDX2jEuwq8n5TTN@shell.armlinux.org.uk> (raw)
In-Reply-To: <202404180634.GZNTrBPU-lkp@intel.com>
On Thu, Apr 18, 2024 at 06:26:42AM +0800, kernel test robot wrote:
> All warnings (new ones prefixed by >>):
>
> >> drivers/net/dsa/xrs700x/xrs700x.c:714:37: warning: 'xrs700x_phylink_mac_ops' defined but not used [-Wunused-const-variable=]
> 714 | static const struct phylink_mac_ops xrs700x_phylink_mac_ops = {
> | ^~~~~~~~~~~~~~~~~~~~~~~
My testing did not produce this warning, so I'm guessing that by default
the kernel does not build with this warning enabled - which seems to be
completely mad. This is not the first time that this has happened... and
it will not be the last while the kernel adopts this policy.
Your follow-up email shows that there are other warnings which will be
spat out with W=1 which will make spotting one new warning difficult,
so this isn't the answer either.
I guess we are now completely reliant on the 0-day robot finding these
cases... which sucks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-04-18 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 22:26 [arm:zii 20/80] drivers/net/dsa/xrs700x/xrs700x.c:714:37: warning: 'xrs700x_phylink_mac_ops' defined but not used kernel test robot
2024-04-18 8:20 ` Russell King (Oracle) [this message]
2024-04-18 10:21 ` Russell King (Oracle)
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=ZiDX2jEuwq8n5TTN@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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).