From: kernel test robot <lkp@intel.com>
To: <cros-kernel-buildreports@googlegroups.com>
Cc: <oe-kbuild-all@lists.linux.dev>
Subject: [android-common:android-mainline-desktop 1/1] drivers/nvme/host/sysfs.c:357:30: sparse: sparse: symbol 'nvme_ns_diag_attr_group' was not declared. Should it be static?
Date: Sun, 23 Aug 2026 20:55:00 +0800 [thread overview]
Message-ID: <202608221628.h6bPNaUQ-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android-mainline-desktop
head: 32fbb9061c7aac9d3b2343d85e199cedf31e1f67
commit: 37afebc79a11bd889fe8e0a98c9ae034c3cff323 [1/1] nvme: add diag attribute group under sysfs
config: i386-randconfig-r122-20260822 (https://download.01.org/0day-ci/archive/20260822/202608221628.h6bPNaUQ-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260822/202608221628.h6bPNaUQ-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Fixes: 37afebc79a11 ("nvme: add diag attribute group under sysfs")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608221628.h6bPNaUQ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/nvme/host/sysfs.c:357:30: sparse: sparse: symbol 'nvme_ns_diag_attr_group' was not declared. Should it be static?
vim +/nvme_ns_diag_attr_group +357 drivers/nvme/host/sysfs.c
356
> 357 const struct attribute_group nvme_ns_diag_attr_group = {
358 .name = "diag",
359 .attrs = nvme_ns_diag_attrs,
360 .is_visible = nvme_ns_diag_attrs_are_visible,
361 };
362
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-23 12:55 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=202608221628.h6bPNaUQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.