From: kernel test robot <lkp@intel.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: arch/mips/ralink/bootrom.c:17:22: sparse: sparse: incorrect type in argument 2 (different address spaces)
Date: Fri, 17 Jul 2020 14:35:25 +0800 [thread overview]
Message-ID: <202007171421.PuWcazuu%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 07a56bb875afbe39dabbf6ba7b83783d166863db
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to define address spaces
date: 4 weeks ago
config: mips-randconfig-s031-20200717 (attached as .config)
compiler: mipsel-linux-gcc (GCC) 9.3.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.2-49-g707c5017-dirty
git checkout 670d0a4b10704667765f7d18f7592993d02783aa
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=mips
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 >>)
>> arch/mips/ralink/bootrom.c:17:22: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void const *data @@ got void [noderef] __iomem *static [toplevel] membase @@
arch/mips/ralink/bootrom.c:17:22: sparse: expected void const *data
>> arch/mips/ralink/bootrom.c:17:22: sparse: got void [noderef] __iomem *static [toplevel] membase
vim +17 arch/mips/ralink/bootrom.c
7a1a44c909fcb4 John Crispin 2013-05-21 14
7a1a44c909fcb4 John Crispin 2013-05-21 15 static int bootrom_show(struct seq_file *s, void *unused)
7a1a44c909fcb4 John Crispin 2013-05-21 16 {
7a1a44c909fcb4 John Crispin 2013-05-21 @17 seq_write(s, membase, BOOTROM_SIZE);
7a1a44c909fcb4 John Crispin 2013-05-21 18
7a1a44c909fcb4 John Crispin 2013-05-21 19 return 0;
7a1a44c909fcb4 John Crispin 2013-05-21 20 }
7a1a44c909fcb4 John Crispin 2013-05-21 21
:::::: The code at line 17 was first introduced by commit
:::::: 7a1a44c909fcb4707b01448a28490d7be366b530 MIPS: ralink: add a bootrom dumper module
:::::: TO: John Crispin <blogic@openwrt.org>
:::::: CC: Ralf Baechle <ralf@linux-mips.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: 33684 bytes --]
reply other threads:[~2020-07-17 6:36 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=202007171421.PuWcazuu%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®