From: Yujie Liu <yujie.liu@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: drivers/comedi/drivers/tests/../ni_stc.h:1140:35: warning: 'range_ni_E_ao_ext' defined but not used
Date: Mon, 6 Nov 2023 17:31:26 +0800 [thread overview]
Message-ID: <ZUiybtcMJGI5ZCF5@yujie-X299> (raw)
In-Reply-To: <2023110641-profusely-factor-b3c5@gregkh>
Hi Greg,
On Mon, Nov 06, 2023 at 10:00:14AM +0100, Greg Kroah-Hartman wrote:
> On Mon, Nov 06, 2023 at 04:49:17PM +0800, kernel test robot wrote:
> > Hi Greg,
> >
> > kernel test robot noticed the following build warnings:
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 1c41041124bd14dd6610da256a3da4e5b74ce6b1
> > commit: 8ffdff6a8cfbdc174a3a390b6f825a277b5bb895 staging: comedi: move out of staging directory
> > date: 2 years, 7 months ago
>
> Have you tested a newer kernel? Testing a 2 1/2 year old commit feels
> odd to me, was this intentional?
We did test new kernels with W=1, and the issue was captured by the
bot, then bisected to this 2 years 7 months ago commit that was likely
to introduce this issue initially. We have no intention of directly
testing a very old commit, and we're sorry that the date info may
cause some misunderstanding.
This can be reproduced by allyesconfig build on v6.6 with W=1:
$ git checkout v6.6
HEAD is now at ffc253263a13 Linux 6.6
$ make ARCH=x86_64 allyesconfig
$ make W=1 ARCH=x86_64 drivers/comedi/drivers/tests/ni_routes_test.o
...
CC drivers/comedi/drivers/tests/ni_routes_test.o
In file included from drivers/comedi/drivers/tests/ni_routes_test.c:22:
drivers/comedi/drivers/tests/../ni_stc.h:1140:35: error: ‘range_ni_E_ao_ext’ defined but not used [-Werror=unused-const-variable=]
1140 | static const struct comedi_lrange range_ni_E_ao_ext;
| ^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[6]: *** [scripts/Makefile.build:243: drivers/comedi/drivers/tests/ni_routes_test.o] Error 1
make[5]: *** [scripts/Makefile.build:480: drivers/comedi/drivers/tests] Error 2
make[4]: *** [scripts/Makefile.build:480: drivers/comedi/drivers] Error 2
make[3]: *** [scripts/Makefile.build:480: drivers/comedi] Error 2
make[2]: *** [scripts/Makefile.build:480: drivers] Error 2
Best Regards,
Yujie
next prev parent reply other threads:[~2023-11-06 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 8:49 drivers/comedi/drivers/tests/../ni_stc.h:1140:35: warning: 'range_ni_E_ao_ext' defined but not used kernel test robot
2023-11-06 9:00 ` Greg Kroah-Hartman
2023-11-06 9:31 ` Yujie Liu [this message]
2023-11-06 9:48 ` Greg Kroah-Hartman
2023-11-07 1:27 ` Yujie Liu
-- strict thread matches above, loose matches on Subject: below --
2024-01-06 10:36 kernel test robot
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=ZUiybtcMJGI5ZCF5@yujie-X299 \
--to=yujie.liu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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