From: kernel test robot <lkp@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: oe-kbuild-all@lists.linux.dev, devel@driverdev.osuosl.org
Subject: [driver-core:virtual_bus_2 2/2] drivers/regulator/dummy.c:59:27: sparse: sparse: symbol 'dummy_regulator_driver' was not declared. Should it be static?
Date: Wed, 5 Feb 2025 11:40:02 +0800 [thread overview]
Message-ID: <202502051136.oWGOGsbe-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git virtual_bus_2
head: bdb2f3a52db4cbbb7bf900190e7a964ea116d44c
commit: bdb2f3a52db4cbbb7bf900190e7a964ea116d44c [2/2] regulator: dummy: convert to use the virtual bus
config: nios2-randconfig-r113-20250205 (https://download.01.org/0day-ci/archive/20250205/202502051136.oWGOGsbe-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250205/202502051136.oWGOGsbe-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/202502051136.oWGOGsbe-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/regulator/dummy.c:59:27: sparse: sparse: symbol 'dummy_regulator_driver' was not declared. Should it be static?
vim +/dummy_regulator_driver +59 drivers/regulator/dummy.c
58
> 59 struct virtual_driver_ops dummy_regulator_driver = {
60 .probe = dummy_regulator_probe,
61 };
62
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-05 3:40 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=202502051136.oWGOGsbe-lkp@intel.com \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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.