From: kernel test robot <lkp@intel.com>
To: Jianpeng Ma <jianpeng.ma@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Coly Li <colyli@suse.de>, Qiaowei Ren <qiaowei.ren@intel.com>
Subject: [colyli-bcache:nvdimm-meta 2/13] drivers/md/bcache/nvmpg_format.h:132:19: warning: 'bch_nvmpg_recs_magic' defined but not used
Date: Mon, 4 Jul 2022 17:39:33 +0800 [thread overview]
Message-ID: <202207041709.LF2RG54z-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/colyli/linux-bcache.git nvdimm-meta
head: 3c4203ddfa7a07f447f3b497d1ed41cbfce79d8a
commit: 6594f1f01b84315bed570f483e004e5827cb3f92 [2/13] bcache: initialize the nvm pages allocator
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220704/202207041709.LF2RG54z-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/colyli/linux-bcache.git/commit/?id=6594f1f01b84315bed570f483e004e5827cb3f92
git remote add colyli-bcache https://git.kernel.org/pub/scm/linux/kernel/git/colyli/linux-bcache.git
git fetch --no-tags colyli-bcache nvdimm-meta
git checkout 6594f1f01b84315bed570f483e004e5827cb3f92
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/md/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from drivers/md/bcache/nvmpg.h:8,
from drivers/md/bcache/super.c:17:
>> drivers/md/bcache/nvmpg_format.h:132:19: warning: 'bch_nvmpg_recs_magic' defined but not used [-Wunused-const-variable=]
132 | static const __u8 bch_nvmpg_recs_magic[] = {
| ^~~~~~~~~~~~~~~~~~~~
>> drivers/md/bcache/nvmpg_format.h:129:19: warning: 'bch_nvmpg_magic' defined but not used [-Wunused-const-variable=]
129 | static const __u8 bch_nvmpg_magic[] = {
| ^~~~~~~~~~~~~~~
vim +/bch_nvmpg_recs_magic +132 drivers/md/bcache/nvmpg_format.h
17acc4fd6eeb31 Coly Li 2021-07-26 128
17acc4fd6eeb31 Coly Li 2021-07-26 @129 static const __u8 bch_nvmpg_magic[] = {
17acc4fd6eeb31 Coly Li 2021-07-26 130 0x17, 0xbd, 0x53, 0x7f, 0x1b, 0x23, 0xd6, 0x83,
17acc4fd6eeb31 Coly Li 2021-07-26 131 0x46, 0xa4, 0xf8, 0x28, 0x17, 0xda, 0xec, 0xa9 };
17acc4fd6eeb31 Coly Li 2021-07-26 @132 static const __u8 bch_nvmpg_recs_magic[] = {
17acc4fd6eeb31 Coly Li 2021-07-26 133 0x39, 0x25, 0x3f, 0xf7, 0x27, 0x17, 0xd0, 0xb9,
17acc4fd6eeb31 Coly Li 2021-07-26 134 0x10, 0xe6, 0xd2, 0xda, 0x38, 0x68, 0x26, 0xae };
17acc4fd6eeb31 Coly Li 2021-07-26 135
:::::: The code at line 132 was first introduced by commit
:::::: 17acc4fd6eeb31ad4fd73c11e2ef083889030226 bcache: add initial data structures for nvm pages
:::::: TO: Coly Li <colyli@suse.de>
:::::: CC: Coly Li <colyli@suse.de>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-07-04 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 9:39 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-04 9:40 [colyli-bcache:nvdimm-meta 2/13] drivers/md/bcache/nvmpg_format.h:132:19: warning: 'bch_nvmpg_recs_magic' defined but not used 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=202207041709.LF2RG54z-lkp@intel.com \
--to=lkp@intel.com \
--cc=colyli@suse.de \
--cc=jianpeng.ma@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiaowei.ren@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