From: kernel test robot <lkp@intel.com>
To: Thara Gopinath <thara.gopinath@linaro.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [vireshk-pm:cpufreq/arm/linux-next 15/17] drivers/base/arch_topology.c:156:9: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Tue, 24 Aug 2021 23:57:43 +0800 [thread overview]
Message-ID: <202108242312.DH3jDsOZ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2449 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git cpufreq/arm/linux-next
head: 028068a13c533046fd4e37f06fb6efe50c759892
commit: 942914c2f2438d137bcb9b9cb8343de62dc482df [15/17] cpufreq: qcom-cpufreq-hw: Add dcvs interrupt support
config: riscv-randconfig-s032-20210824 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.3-348-gf0e6938b-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git/commit/?id=942914c2f2438d137bcb9b9cb8343de62dc482df
git remote add vireshk-pm https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git
git fetch --no-tags vireshk-pm cpufreq/arm/linux-next
git checkout 942914c2f2438d137bcb9b9cb8343de62dc482df
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/base/arch_topology.c:156:9: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected void const [noderef] __percpu *__vpp_verify @@ got unsigned long * @@
drivers/base/arch_topology.c:156:9: sparse: expected void const [noderef] __percpu *__vpp_verify
drivers/base/arch_topology.c:156:9: sparse: got unsigned long *
vim +156 drivers/base/arch_topology.c
2ef7a2953c81ee Juri Lelli 2017-05-31 153
4ca4f26a9c6610 Juri Lelli 2017-05-31 154 void topology_set_cpu_scale(unsigned int cpu, unsigned long capacity)
2ef7a2953c81ee Juri Lelli 2017-05-31 155 {
2ef7a2953c81ee Juri Lelli 2017-05-31 @156 per_cpu(cpu_scale, cpu) = capacity;
2ef7a2953c81ee Juri Lelli 2017-05-31 157 }
2ef7a2953c81ee Juri Lelli 2017-05-31 158
:::::: The code at line 156 was first introduced by commit
:::::: 2ef7a2953c81ee6b341e3ffb33570adc894cf4a5 arm, arm64: factorize common cpu capacity default code
:::::: TO: Juri Lelli <juri.lelli@arm.com>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30272 bytes --]
next reply other threads:[~2021-08-24 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 15:57 kernel test robot [this message]
2021-08-25 3:32 ` [vireshk-pm:cpufreq/arm/linux-next 15/17] drivers/base/arch_topology.c:156:9: sparse: sparse: incorrect type in initializer (different address spaces) Viresh Kumar
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=202108242312.DH3jDsOZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thara.gopinath@linaro.org \
--cc=viresh.kumar@linaro.org \
/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