public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jerome Brunet <jbrunet@baylibre.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: sound/soc/meson/t9015.c:315:34: warning: unused variable 't9015_ids'
Date: Wed, 10 Jun 2020 17:31:03 +0200	[thread overview]
Message-ID: <1jftb32b0o.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <202005311147.iLK0hQoe%lkp@intel.com>


On Sun 31 May 2020 at 05:00, kbuild test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   ffeb595d84811dde16a28b33d8a7cf26d51d51b3
> commit: 33901f5b9b16d212ee58865e9e8e80fc813f12da ASoC: meson: add t9015 internal DAC driver
> date:   3 months ago
> config: x86_64-randconfig-r033-20200531 (attached as .config)
> compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 2388a096e7865c043e83ece4e26654bd3d1a20d5)
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # install x86_64 cross compiling tool for clang build
>         # apt-get install binutils-x86-64-linux-gnu
>         git checkout 33901f5b9b16d212ee58865e9e8e80fc813f12da
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>, old ones prefixed by <<):
>
>>> sound/soc/meson/t9015.c:315:34: warning: unused variable 't9015_ids' [-Wunused-const-variable]
> static const struct of_device_id t9015_ids[] = {
> ^
> 1 warning generated.
>
> vim +/t9015_ids +315 sound/soc/meson/t9015.c
>
>    314	
>  > 315	static const struct of_device_id t9015_ids[] = {
>    316		{ .compatible = "amlogic,t9015", },
>    317		{ }
>    318	};
>    319	MODULE_DEVICE_TABLE(of, t9015_ids);
>    320	

Hi,

I'm not sure what to do with this report.
I tried to reproduce has instructed, the log is full of warnings and the
compilation eventually fails to link.

It seems that most (if not all) drivers with a MODULE_DEVICE_TABLE() show
this warning with the provided .config (COMPILE_TEST).

When compiled with gcc, no such warning is shown.
I can remove COMPILE_TEST for this driver, it will make the warning go
away but I'm not sure it is appropriate.

>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org


  reply	other threads:[~2020-06-10 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31  3:00 sound/soc/meson/t9015.c:315:34: warning: unused variable 't9015_ids' kbuild test robot
2020-06-10 15:31 ` Jerome Brunet [this message]
2020-06-10 16:39   ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2020-06-22  9:47 kernel test robot
2020-07-26 20:54 kernel test robot
2020-09-18  6:37 kernel test robot
2020-09-27  1:43 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=1jftb32b0o.fsf@starbuckisacylon.baylibre.com \
    --to=jbrunet@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.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