From: kernel test robot <lkp@intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [l1k:mariusz-npem 3/3] drivers/pci/npem.c:363:23: sparse: sparse: symbol 'dsm_ops' was not declared. Should it be static?
Date: Wed, 29 May 2024 06:50:32 +0800 [thread overview]
Message-ID: <202405290643.bDL3GC4x-lkp@intel.com> (raw)
tree: https://github.com/l1k/linux mariusz-npem
head: 2fb114bf74eff73c83383cbd1d481584053cb8cd
commit: 2fb114bf74eff73c83383cbd1d481584053cb8cd [3/3] PCI/NPEM: Add _DSM PCIe SSD status LED management
config: x86_64-randconfig-123-20240528 (https://download.01.org/0day-ci/archive/20240529/202405290643.bDL3GC4x-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240529/202405290643.bDL3GC4x-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
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202405290643.bDL3GC4x-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/pci/npem.c:229:23: sparse: sparse: symbol 'npem_ops' was not declared. Should it be static?
>> drivers/pci/npem.c:363:23: sparse: sparse: symbol 'dsm_ops' was not declared. Should it be static?
vim +/dsm_ops +363 drivers/pci/npem.c
362
> 363 const struct npem_ops dsm_ops = {
364 .inds = dsm_indications,
365 .get_active_indications = dsm_get_active_indications,
366 .set_active_indications = dsm_set_active_indications,
367 };
368
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-28 22:51 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=202405290643.bDL3GC4x-lkp@intel.com \
--to=lkp@intel.com \
--cc=lukas@wunner.de \
--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.