From: kernel test robot <lkp@intel.com>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
linux-kernel@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Daniel Thompson <daniel.thompson@linaro.org>
Subject: drivers/char/hw_random/npcm-rng.c:166:34: warning: unused variable 'rng_dt_id'
Date: Tue, 23 Jun 2020 21:58:39 +0800 [thread overview]
Message-ID: <202006232136.vz36SNV9%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]
Hi Tomer,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: dd0d718152e4c65b173070d48ea9dfc06894c3e5
commit: c98429297d8b25a0d9c48d8e1f5237f19412f07b hwrng: npcm - add NPCM RNG driver
date: 9 months ago
config: x86_64-randconfig-r004-20200623 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 1d4c87335d5236ea1f35937e1014980ba961ae34)
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 c98429297d8b25a0d9c48d8e1f5237f19412f07b
# 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: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/char/hw_random/npcm-rng.c:166:34: warning: unused variable 'rng_dt_id' [-Wunused-const-variable]
static const struct of_device_id rng_dt_id[] = {
^
1 warning generated.
vim +/rng_dt_id +166 drivers/char/hw_random/npcm-rng.c
165
> 166 static const struct of_device_id rng_dt_id[] = {
167 { .compatible = "nuvoton,npcm750-rng", },
168 {},
169 };
170 MODULE_DEVICE_TABLE(of, rng_dt_id);
171
---
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: 37856 bytes --]
next reply other threads:[~2020-06-23 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 13:58 kernel test robot [this message]
2020-06-26 6:42 ` drivers/char/hw_random/npcm-rng.c:166:34: warning: unused variable 'rng_dt_id' Herbert Xu
2020-06-26 6:52 ` Nathan Chancellor
2020-06-29 8:02 ` Herbert Xu
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=202006232136.vz36SNV9%lkp@intel.com \
--to=lkp@intel.com \
--cc=clang-built-linux@googlegroups.com \
--cc=daniel.thompson@linaro.org \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmaimon77@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