All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [stffrdhrn:starfive-bad-dcache-flush 4/39] drivers/char/hw_random/starfive-vic-rng.c:238:34: warning: unused variable 'vic_rng_dt_ids'
Date: Sun, 23 May 2021 01:21:34 +0800	[thread overview]
Message-ID: <202105230127.J8K5JUVN-lkp@intel.com> (raw)

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

CC: kbuild-all(a)lists.01.org
CC: clang-built-linux(a)googlegroups.com
TO: Huan Feng <huan.feng@starfivetech.com>
CC: Emil Renner Berthing <kernel@esmil.dk>

tree:   https://github.com/stffrdhrn/linux.git starfive-bad-dcache-flush
head:   a5c948a9cc2b8944f00056c067fb7bde19b34843
commit: c9f02856ce72f3de501b56484ecdc71e261fdaa5 [4/39] drivers/hw_random: Add Starfive VIC Random Number Generator driver
:::::: branch date: 33 hours ago
:::::: commit date: 6 days ago
config: x86_64-randconfig-b001-20210522 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project e84a9b9bb3051c35dea993cdad7b3d2575638f85)
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://github.com/stffrdhrn/linux/commit/c9f02856ce72f3de501b56484ecdc71e261fdaa5
        git remote add stffrdhrn https://github.com/stffrdhrn/linux.git
        git fetch --no-tags stffrdhrn starfive-bad-dcache-flush
        git checkout c9f02856ce72f3de501b56484ecdc71e261fdaa5
        # 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/starfive-vic-rng.c:238:34: warning: unused variable 'vic_rng_dt_ids' [-Wunused-const-variable]
   static const struct of_device_id vic_rng_dt_ids[] = {
                                    ^
   1 warning generated.


vim +/vic_rng_dt_ids +238 drivers/char/hw_random/starfive-vic-rng.c

c9f02856ce72f3 Huan Feng 2021-01-08  237  
c9f02856ce72f3 Huan Feng 2021-01-08 @238  static const struct of_device_id vic_rng_dt_ids[] = {
c9f02856ce72f3 Huan Feng 2021-01-08  239  	{ .compatible = "starfive,vic-rng" },
c9f02856ce72f3 Huan Feng 2021-01-08  240  	{ }
c9f02856ce72f3 Huan Feng 2021-01-08  241  };
c9f02856ce72f3 Huan Feng 2021-01-08  242  MODULE_DEVICE_TABLE(of, vic_rng_dt_ids);
c9f02856ce72f3 Huan Feng 2021-01-08  243  

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

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

             reply	other threads:[~2021-05-22 17:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 17:21 kernel test robot [this message]
2021-05-23  8:20 [stffrdhrn:starfive-bad-dcache-flush 4/39] drivers/char/hw_random/starfive-vic-rng.c:238:34: warning: unused variable 'vic_rng_dt_ids' kernel test robot
2021-05-24  0:53 kernel test robot
2021-05-24  1:40 ` Huan Feng
2021-05-24  2:34   ` Rong Chen
2021-05-24  6:38   ` Rong Chen

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=202105230127.J8K5JUVN-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.