linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: sound/soc/codecs/zl38060.c:614:34: warning: unused variable 'zl38_dt_ids'
Date: Thu, 6 May 2021 13:42:38 +0800	[thread overview]
Message-ID: <202105061332.nmVjqKVj-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

Hi Sven,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   8404c9fbc84b741f66cff7d4934a25dd2c344452
commit: 52e8a94baf9026276fcdc9ff21a50dc2ca0bc94b ASoC: Add initial ZL38060 driver
date:   1 year ago
config: x86_64-randconfig-a001-20210506 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 8f5a2a5836cc8e4c1def2bdeb022e7b496623439)
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
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=52e8a94baf9026276fcdc9ff21a50dc2ca0bc94b
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout 52e8a94baf9026276fcdc9ff21a50dc2ca0bc94b
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> sound/soc/codecs/zl38060.c:614:34: warning: unused variable 'zl38_dt_ids' [-Wunused-const-variable]
   static const struct of_device_id zl38_dt_ids[] = {
                                    ^
   1 warning generated.


vim +/zl38_dt_ids +614 sound/soc/codecs/zl38060.c

   613	
 > 614	static const struct of_device_id zl38_dt_ids[] = {
   615		{ .compatible = "mscc,zl38060", },
   616		{ /* sentinel */ }
   617	};
   618	MODULE_DEVICE_TABLE(of, zl38_dt_ids);
   619	

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32293 bytes --]

             reply	other threads:[~2021-05-06  5:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06  5:42 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-12 19:17 sound/soc/codecs/zl38060.c:614:34: warning: unused variable 'zl38_dt_ids' kernel test robot
2020-09-19 17:56 kernel test robot
2020-07-09 16:47 kernel test robot
2020-07-10  2:41 ` Nathan Chancellor
2020-07-10 12:24   ` Mark Brown
2020-07-11  3:30     ` Nathan Chancellor
2020-07-11 15:08       ` Sven Van Asbroeck
2020-07-06  2:49 kernel test robot
2020-06-17  8: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=202105061332.nmVjqKVj-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=broonie@kernel.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thesven73@gmail.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;
as well as URLs for NNTP newsgroup(s).