From: kernel test robot <lkp@intel.com>
To: Julien Massot <julien.massot@iot.bzh>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: drivers/remoteproc/rcar_rproc.c:45:20: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sun, 17 Jul 2022 04:25:49 +0800 [thread overview]
Message-ID: <202207170418.y871sITG-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c5fe7a97f20c7f3070ac870144515c0fabc6b999
commit: 285892a74f1370a12249f765c6a4e3b16194852e remoteproc: Add Renesas rcar driver
date: 7 months ago
config: arc-randconfig-s043-20220717 (https://download.01.org/0day-ci/archive/20220717/202207170418.y871sITG-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 12.1.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.4-39-gce1a6720-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=285892a74f1370a12249f765c6a4e3b16194852e
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 285892a74f1370a12249f765c6a4e3b16194852e
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arc SHELL=/bin/bash drivers/remoteproc/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
drivers/remoteproc/rcar_rproc.c:28:12: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *va @@ got void [noderef] __iomem * @@
drivers/remoteproc/rcar_rproc.c:28:12: sparse: expected void *va
drivers/remoteproc/rcar_rproc.c:28:12: sparse: got void [noderef] __iomem *
>> drivers/remoteproc/rcar_rproc.c:45:20: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const [noderef] __iomem *addr @@ got void *va @@
drivers/remoteproc/rcar_rproc.c:45:20: sparse: expected void const [noderef] __iomem *addr
drivers/remoteproc/rcar_rproc.c:45:20: sparse: got void *va
vim +45 drivers/remoteproc/rcar_rproc.c
40
41 static int rcar_rproc_mem_release(struct rproc *rproc,
42 struct rproc_mem_entry *mem)
43 {
44 dev_dbg(&rproc->dev, "unmap memory: %pa\n", &mem->dma);
> 45 iounmap(mem->va);
46
47 return 0;
48 }
49
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-07-16 20:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 20:25 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-25 20:30 drivers/remoteproc/rcar_rproc.c:45:20: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2023-12-14 7:35 kernel test robot
2023-12-07 13:39 kernel test robot
2023-12-07 0:17 kernel test robot
2023-12-05 14:38 kernel test robot
2023-12-01 7:41 kernel test robot
2023-03-10 11:25 kernel test robot
2022-11-02 2:56 kernel test robot
2022-11-01 19:52 kernel test robot
2022-11-01 14:18 kernel test robot
2022-10-20 21:37 kernel test robot
2022-09-22 8:20 kernel test robot
2022-08-05 19:20 kernel test robot
2022-07-09 21:29 kernel test robot
2022-06-04 11:30 kernel test robot
2022-03-24 8:35 kernel test robot
2022-03-11 4:58 kernel test robot
2022-03-09 16:40 kernel test robot
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=202207170418.y871sITG-lkp@intel.com \
--to=lkp@intel.com \
--cc=julien.massot@iot.bzh \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@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