From: kernel test robot <lkp@intel.com>
To: Stafford Horne <shorne@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: drivers/video/fbdev/sstfb.c:337:23: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sun, 5 Feb 2023 06:15:41 +0800 [thread overview]
Message-ID: <202302050615.2F4POBYV-lkp@intel.com> (raw)
Hi Stafford,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: db27c22251e7c8f3a9d5bfb55c9c8c701a70bbb3
commit: ded2ee36313c941f1a12b6f85cde295b575264ae openrisc: Add pci bus support
date: 6 months ago
config: openrisc-randconfig-s032-20230205 (https://download.01.org/0day-ci/archive/20230205/202302050615.2F4POBYV-lkp@intel.com/config)
compiler: or1k-linux-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=ded2ee36313c941f1a12b6f85cde295b575264ae
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout ded2ee36313c941f1a12b6f85cde295b575264ae
# 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=openrisc olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=openrisc SHELL=/bin/bash drivers/video/fbdev/
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/video/fbdev/sstfb.c:337:23: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *s @@ got char [noderef] __iomem *screen_base @@
drivers/video/fbdev/sstfb.c:337:23: sparse: expected void *s
drivers/video/fbdev/sstfb.c:337:23: sparse: got char [noderef] __iomem *screen_base
vim +337 drivers/video/fbdev/sstfb.c
^1da177e4c3f41 drivers/video/sstfb.c Linus Torvalds 2005-04-16 330
^1da177e4c3f41 drivers/video/sstfb.c Linus Torvalds 2005-04-16 331 /*
^1da177e4c3f41 drivers/video/sstfb.c Linus Torvalds 2005-04-16 332 * clear lfb screen
^1da177e4c3f41 drivers/video/sstfb.c Linus Torvalds 2005-04-16 333 */
^1da177e4c3f41 drivers/video/sstfb.c Linus Torvalds 2005-04-16 334 static void sstfb_clear_screen(struct fb_info *info)
^1da177e4c3f41 drivers/video/sstfb.c Linus Torvalds 2005-04-16 335 {
^1da177e4c3f41 drivers/video/sstfb.c Linus Torvalds 2005-04-16 336 /* clear screen */
^1da177e4c3f41 drivers/video/sstfb.c Linus Torvalds 2005-04-16 @337 fb_memset(info->screen_base, 0, info->fix.smem_len);
^1da177e4c3f41 drivers/video/sstfb.c Linus Torvalds 2005-04-16 338 }
^1da177e4c3f41 drivers/video/sstfb.c Linus Torvalds 2005-04-16 339
:::::: The code at line 337 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-02-04 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 22:15 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-25 20:10 drivers/video/fbdev/sstfb.c:337:23: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2020-08-08 6:16 kernel test robot
2020-08-07 12:27 kernel test robot
2020-07-09 14:29 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=202302050615.2F4POBYV-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shorne@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