From: kernel test robot <lkp@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: oe-kbuild-all@lists.linux.dev, linux-hwmon@vger.kernel.org
Subject: drivers/hwmon/pmbus/pmbus_core.c:3507:33: sparse: sparse: symbol 'pmbus_debugfs_block_data' was not declared. Should it be static?
Date: Wed, 5 Feb 2025 04:24:01 +0800 [thread overview]
Message-ID: <202502050447.CA5dAMMU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git testing
head: 67b0f0fb646de244e59420a373c93a9deb2c60b5
commit: 9fac9564cf8a1da1d26a555355cb92b517444b1e hwmon: (pmbus/core) Optimize debugfs block data attribute initialization
date: 25 hours ago
config: csky-randconfig-r132-20250205 (https://download.01.org/0day-ci/archive/20250205/202502050447.CA5dAMMU-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250205/202502050447.CA5dAMMU-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/202502050447.CA5dAMMU-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/hwmon/pmbus/pmbus_core.c:3507:33: sparse: sparse: symbol 'pmbus_debugfs_block_data' was not declared. Should it be static?
vim +/pmbus_debugfs_block_data +3507 drivers/hwmon/pmbus/pmbus_core.c
3506
> 3507 const struct pmbus_debugfs_data pmbus_debugfs_block_data[] = {
3508 { .reg = PMBUS_MFR_ID, .name = "mfr_id" },
3509 { .reg = PMBUS_MFR_MODEL, .name = "mfr_model" },
3510 { .reg = PMBUS_MFR_REVISION, .name = "mfr_revision" },
3511 { .reg = PMBUS_MFR_LOCATION, .name = "mfr_location" },
3512 { .reg = PMBUS_MFR_DATE, .name = "mfr_date" },
3513 { .reg = PMBUS_MFR_SERIAL, .name = "mfr_serial" },
3514 };
3515
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-04 20:24 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=202502050447.CA5dAMMU-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox