linux-kernel - [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=]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <3bab8580-c01a-4183-94af-ba3193c94c0e@gmail.com>
Date: Tue, 9 Jul 2024 23:42:49 +0200
From: Mirsad Todorovac <mtodorovac69@...il.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc: Ian Abbott <abbotti@....co.uk>,
 H Hartley Sweeten <hsweeten@...ionengravers.com>,
 Michael Hennerich <michael.hennerich@...log.com>,
 Peter Rosin <peda@...ntia.se>, linux-i2c@...r.kernel.org,
 York Sun <yorksun@...escale.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=]

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