From: kernel test robot <lkp@intel.com>
To: Binbin Zhou <zhoubinbin@loongson.cn>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Corey Minyard <corey@minyard.net>,
Chong Qiao <qiaochong@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>
Subject: drivers/char/ipmi/ipmi_si_ls2k.c:171:24: sparse: sparse: symbol 'ipmi_ls2k_platform_driver' was not declared. Should it be static?
Date: Sat, 17 Jan 2026 07:11:02 +0800 [thread overview]
Message-ID: <202601170753.3zDBerGP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b62ce2547fe8a8ba15857bb974bcad250c5420d6
commit: d46651d4e3c0caab554c4c591c0b6c3b026b1e93 ipmi: Add Loongson-2K BMC support
date: 4 months ago
config: loongarch-randconfig-r112-20260116 (https://download.01.org/0day-ci/archive/20260117/202601170753.3zDBerGP-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260117/202601170753.3zDBerGP-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/202601170753.3zDBerGP-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/char/ipmi/ipmi_si_ls2k.c:171:24: sparse: sparse: symbol 'ipmi_ls2k_platform_driver' was not declared. Should it be static?
vim +/ipmi_ls2k_platform_driver +171 drivers/char/ipmi/ipmi_si_ls2k.c
170
> 171 struct platform_driver ipmi_ls2k_platform_driver = {
172 .driver = {
173 .name = "ls2k-ipmi-si",
174 },
175 .probe = ipmi_ls2k_probe,
176 .remove = ipmi_ls2k_remove,
177 };
178
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-16 23:11 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=202601170753.3zDBerGP-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenhuacai@loongson.cn \
--cc=corey@minyard.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=qiaochong@loongson.cn \
--cc=zhoubinbin@loongson.cn \
/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.