From: Mirsad Todorovac <mtodorovac69@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Ian Abbott <abbotti@mev.co.uk>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Michael Hennerich <michael.hennerich@analog.com>,
Peter Rosin <peda@axentia.se>,
linux-i2c@vger.kernel.org, York Sun <yorksun@freescale.com>
Subject: [PROBLEM linux-next] drivers/comedi/drivers/tests/../ni_stc.h:1140:35: error: ‘range_ni_E_ao_ext’ defined but not used [-Werror=unused-const-variable=]
Date: Tue, 9 Jul 2024 23:42:49 +0200 [thread overview]
Message-ID: <3bab8580-c01a-4183-94af-ba3193c94c0e@gmail.com> (raw)
Dear all,
On the linux-next vanilla next-20240709 tree, I have attempted the seed KCONFIG_SEED=0xEE7AB52F
which was known from before to trigger various errors in compile and build process.
Though this might seem as contributing to channel noise, Linux refuses to build this config,
treating warnings as errors, using this build line:
$ time nice make W=1 -k -j 36 |& tee ../err-next-20230709-01a.log; date
As I know that the Chief Penguin doesn't like warnings, but I am also aware that there are plenty
left, there seems to be more tedious work ahead to make the compilers happy.
The compiler output is:
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;
| ^~~~~~~~~~~~~~~~~
drivers/i2c/muxes/i2c-mux-ltc4306.c:200:34: error: ‘ltc4306_of_match’ defined but not used [-Werror=unused-const-variable=]
200 | static const struct of_device_id ltc4306_of_match[] = {
| ^~~~~~~~~~~~~~~~
drivers/i2c/muxes/i2c-mux-reg.c:242:34: error: ‘i2c_mux_reg_of_match’ defined but not used [-Werror=unused-const-variable=]
242 | static const struct of_device_id i2c_mux_reg_of_match[] = {
| ^~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
cc1: all warnings being treated as errors
------------------------------------------------------------------
1139
→ 1140 static const struct comedi_lrange range_ni_E_ao_ext;
1141
------------------------------------------------------------------
199
→ 200 static const struct of_device_id ltc4306_of_match[] = {
201 { .compatible = "lltc,ltc4305", .data = &chips[ltc_4305] },
------------------------------------------------------------------
239 i2c_put_adapter(muxc->parent);
240 }
241
→ 242 static const struct of_device_id i2c_mux_reg_of_match[] = {
243 { .compatible = "i2c-mux-reg", },
244 {},
245 };
------------------------------------------------------------------
These are just unused variables, so to repeat I might be adding to the noise, but in certain configs they
prevent build success.
Hope this helps.
Best regards,
Mirsad Todorovac
reply other threads:[~2024-07-09 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3bab8580-c01a-4183-94af-ba3193c94c0e@gmail.com \
--to=mtodorovac69@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=hsweeten@visionengravers.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=peda@axentia.se \
--cc=yorksun@freescale.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