From: kernel test robot <lkp@intel.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Mark Brown <broonie@kernel.org>
Subject: [linux-next:master 865/1400] drivers/regulator/qcom_smd-regulator.c:14:21: sparse: sparse: symbol 'smd_vreg_rpm' was not declared. Should it be static?
Date: Wed, 24 Jan 2024 01:42:59 +0800 [thread overview]
Message-ID: <202401240123.wBsFom3Z-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 774551425799cb5bbac94e1768fd69eec4f78dd4
commit: 5df3b41bd6b5432010d6d85e5aa7217bd8f6b0cb [865/1400] regulator: qcom_smd: Keep one rpm handle for all vregs
config: microblaze-randconfig-r123-20240123 (https://download.01.org/0day-ci/archive/20240124/202401240123.wBsFom3Z-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240124/202401240123.wBsFom3Z-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/202401240123.wBsFom3Z-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/regulator/qcom_smd-regulator.c:14:21: sparse: sparse: symbol 'smd_vreg_rpm' was not declared. Should it be static?
vim +/smd_vreg_rpm +14 drivers/regulator/qcom_smd-regulator.c
13
> 14 struct qcom_smd_rpm *smd_vreg_rpm;
15
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-23 17:43 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=202401240123.wBsFom3Z-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox