From: kernel test robot <lkp@intel.com>
To: Tanmay Shah <tanmay.shah@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Ben Levinsky <ben.levinsky@amd.com>
Subject: drivers/remoteproc/xlnx_r5_remoteproc.c:209:20: sparse: sparse: cast removes address space '__iomem' of expression
Date: Sun, 5 Nov 2023 15:29:21 +0800 [thread overview]
Message-ID: <202311051552.fmM6xtjE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: aea6bf908d730b01bd264a8821159db9463c111c
commit: 6b291e8020a8bd90e94ee13d61f251040425c90d drivers: remoteproc: Add Xilinx r5 remoteproc driver
date: 12 months ago
config: arm64-randconfig-r122-20231102 (https://download.01.org/0day-ci/archive/20231105/202311051552.fmM6xtjE-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231105/202311051552.fmM6xtjE-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/202311051552.fmM6xtjE-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/remoteproc/xlnx_r5_remoteproc.c:209:20: sparse: sparse: cast removes address space '__iomem' of expression
drivers/remoteproc/xlnx_r5_remoteproc.c:315:20: sparse: sparse: cast removes address space '__iomem' of expression
vim +/__iomem +209 drivers/remoteproc/xlnx_r5_remoteproc.c
190
191 /*
192 * zynqmp_r5_mem_region_map()
193 * @rproc: single R5 core's corresponding rproc instance
194 * @mem: mem descriptor to map reserved memory-regions
195 *
196 * Callback to map va for memory-region's carveout.
197 *
198 * return 0 on success, otherwise non-zero value on failure
199 */
200 static int zynqmp_r5_mem_region_map(struct rproc *rproc,
201 struct rproc_mem_entry *mem)
202 {
203 void __iomem *va;
204
205 va = ioremap_wc(mem->dma, mem->len);
206 if (IS_ERR_OR_NULL(va))
207 return -ENOMEM;
208
> 209 mem->va = (void *)va;
210
211 return 0;
212 }
213
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-05 7:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 7:29 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-03 23:30 drivers/remoteproc/xlnx_r5_remoteproc.c:209:20: sparse: sparse: cast removes address space '__iomem' of expression kernel test robot
2023-11-02 22:36 kernel test robot
2023-05-15 23:06 kernel test robot
2023-04-13 15:18 kernel test robot
2023-03-29 15:30 kernel test robot
2023-03-19 3:08 kernel test robot
2023-01-11 0:29 kernel test robot
2022-12-25 1:32 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=202311051552.fmM6xtjE-lkp@intel.com \
--to=lkp@intel.com \
--cc=ben.levinsky@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tanmay.shah@amd.com \
/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.