From: kernel test robot <lkp@intel.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [bvanassche:scsi-for-next 2/2] drivers/scsi/smartpqi/smartpqi_init.c:6927:26: error: 'pqi_sdev_attrs' defined but not used
Date: Thu, 11 Nov 2021 22:21:42 +0800 [thread overview]
Message-ID: <202111112233.OaZNCkqT-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]
tree: https://github.com/bvanassche/linux scsi-for-next
head: 3d4f1af1fe85f0f2cc435ea177d25f9bad454965
commit: 3d4f1af1fe85f0f2cc435ea177d25f9bad454965 [2/2] scsi: Register SCSI device sysfs attributes earlier
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-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://github.com/bvanassche/linux/commit/3d4f1af1fe85f0f2cc435ea177d25f9bad454965
git remote add bvanassche https://github.com/bvanassche/linux
git fetch --no-tags bvanassche scsi-for-next
git checkout 3d4f1af1fe85f0f2cc435ea177d25f9bad454965
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=xtensa
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 >>):
drivers/scsi/smartpqi/smartpqi_init.c:6952:29: error: 'pqi_sdev_attr_groups' undeclared here (not in a function); did you mean 'pqi_shost_attr_groups'?
6952 | .sdev_attr_groups = pqi_sdev_attr_groups,
| ^~~~~~~~~~~~~~~~~~~~
| pqi_shost_attr_groups
>> drivers/scsi/smartpqi/smartpqi_init.c:6927:26: error: 'pqi_sdev_attrs' defined but not used [-Werror=unused-variable]
6927 | static struct attribute *pqi_sdev_attrs[] = {
| ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/pqi_sdev_attrs +6927 drivers/scsi/smartpqi/smartpqi_init.c
6926
> 6927 static struct attribute *pqi_sdev_attrs[] = {
6928 &dev_attr_lunid.attr,
6929 &dev_attr_unique_id.attr,
6930 &dev_attr_path_info.attr,
6931 &dev_attr_sas_address.attr,
6932 &dev_attr_ssd_smart_path_enabled.attr,
6933 &dev_attr_raid_level.attr,
6934 &dev_attr_raid_bypass_cnt.attr,
6935 NULL
6936 };
6937
---
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: 68943 bytes --]
reply other threads:[~2021-11-11 14:22 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=202111112233.OaZNCkqT-lkp@intel.com \
--to=lkp@intel.com \
--cc=bvanassche@acm.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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 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®