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 12/23] drivers/md/bcache/nvmpg_format.h:132:19: error: 'bch_nvmpg_recs_magic' defined but not used
Date: Thu, 28 Oct 2021 15:59:49 +0800 [thread overview]
Message-ID: <202110281541.DJZzHPmd-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2805 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/colyli/linux-bcache.git nvdimm-meta
head: 544e57301b9adc7628556f4b709f65c35142df47
commit: d0a096b054485476b6788ae2a071c036dcffc248 [12/23] bcache: initialize the nvm pages allocator
config: openrisc-buildonly-randconfig-r001-20211027 (attached as .config)
compiler: or1k-linux-gcc (GCC) 11.2.0
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
# https://git.kernel.org/pub/scm/linux/kernel/git/colyli/linux-bcache.git/commit/?id=d0a096b054485476b6788ae2a071c036dcffc248
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 d0a096b054485476b6788ae2a071c036dcffc248
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=openrisc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (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: error: 'bch_nvmpg_recs_magic' defined but not used [-Werror=unused-const-variable=]
132 | static const __u8 bch_nvmpg_recs_magic[] = {
| ^~~~~~~~~~~~~~~~~~~~
>> drivers/md/bcache/nvmpg_format.h:129:19: error: 'bch_nvmpg_magic' defined but not used [-Werror=unused-const-variable=]
129 | static const __u8 bch_nvmpg_magic[] = {
| ^~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/bch_nvmpg_recs_magic +132 drivers/md/bcache/nvmpg_format.h
d5ca176bc66727 Coly Li 2021-07-26 128
d5ca176bc66727 Coly Li 2021-07-26 @129 static const __u8 bch_nvmpg_magic[] = {
d5ca176bc66727 Coly Li 2021-07-26 130 0x17, 0xbd, 0x53, 0x7f, 0x1b, 0x23, 0xd6, 0x83,
d5ca176bc66727 Coly Li 2021-07-26 131 0x46, 0xa4, 0xf8, 0x28, 0x17, 0xda, 0xec, 0xa9 };
d5ca176bc66727 Coly Li 2021-07-26 @132 static const __u8 bch_nvmpg_recs_magic[] = {
d5ca176bc66727 Coly Li 2021-07-26 133 0x39, 0x25, 0x3f, 0xf7, 0x27, 0x17, 0xd0, 0xb9,
d5ca176bc66727 Coly Li 2021-07-26 134 0x10, 0xe6, 0xd2, 0xda, 0x38, 0x68, 0x26, 0xae };
d5ca176bc66727 Coly Li 2021-07-26 135
:::::: The code at line 132 was first introduced by commit
:::::: d5ca176bc66727740baa4c80ba1349ba25dc95f7 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, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32895 bytes --]
reply other threads:[~2021-10-28 8:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202110281541.DJZzHPmd-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
all inboxes | Powered by JetHome®