From: kernel test robot <lkp@intel.com>
To: Florian Fuchs <fuchsfl@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Helge Deller <deller@gmx.de>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: drivers/video/fbdev/pvr2fb.c:730:27: sparse: sparse: incorrect type in initializer (incompatible argument 2 (different address spaces))
Date: Mon, 13 Jul 2026 13:20:55 +0800 [thread overview]
Message-ID: <202607131247.fpQ6eTc7-lkp@intel.com> (raw)
Hi Florian,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 44696aa3a489d2baf58efa61b37833f100072bee
commit: 5f566c0ac51cd2474e47da68dbe719d3acf7d999 fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS
date: 9 months ago
config: sh-randconfig-r111-20260713 (https://download.01.org/0day-ci/archive/20260713/202607131247.fpQ6eTc7-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 10.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260713/202607131247.fpQ6eTc7-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
| Fixes: 5f566c0ac51c ("fbdev: pvr2fb: Fix leftover reference to ONCHIP_NR_DMA_CHANNELS")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202607131247.fpQ6eTc7-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/video/fbdev/pvr2fb.c:730:27: sparse: sparse: incorrect type in initializer (incompatible argument 2 (different address spaces)) @@ expected int ( *fb_write )( ... ) @@ got int ( * )( ... ) @@
drivers/video/fbdev/pvr2fb.c:730:27: sparse: expected int ( *fb_write )( ... )
drivers/video/fbdev/pvr2fb.c:730:27: sparse: got int ( * )( ... )
drivers/video/fbdev/pvr2fb.c:1081:11: sparse: sparse: Using plain integer as NULL pointer
vim +730 drivers/video/fbdev/pvr2fb.c
^1da177e4c3f415 drivers/video/pvr2fb.c Linus Torvalds 2005-04-16 725
8a48ac339398f21 drivers/video/fbdev/pvr2fb.c Jani Nikula 2019-12-03 726 static const struct fb_ops pvr2fb_ops = {
db7f2cb965cb792 drivers/video/fbdev/pvr2fb.c Bartlomiej Zolnierkiewicz 2019-06-07 727 .owner = THIS_MODULE,
423273970906070 drivers/video/fbdev/pvr2fb.c Thomas Zimmermann 2023-09-27 728 #ifdef CONFIG_PVR2_DMA
423273970906070 drivers/video/fbdev/pvr2fb.c Thomas Zimmermann 2023-09-27 729 .fb_read = fb_io_read,
423273970906070 drivers/video/fbdev/pvr2fb.c Thomas Zimmermann 2023-09-27 @730 .fb_write = pvr2fb_write,
423273970906070 drivers/video/fbdev/pvr2fb.c Thomas Zimmermann 2023-09-27 731 #else
423273970906070 drivers/video/fbdev/pvr2fb.c Thomas Zimmermann 2023-09-27 732 __FB_DEFAULT_IOMEM_OPS_RDWR,
423273970906070 drivers/video/fbdev/pvr2fb.c Thomas Zimmermann 2023-09-27 733 #endif
db7f2cb965cb792 drivers/video/fbdev/pvr2fb.c Bartlomiej Zolnierkiewicz 2019-06-07 734 .fb_setcolreg = pvr2fb_setcolreg,
db7f2cb965cb792 drivers/video/fbdev/pvr2fb.c Bartlomiej Zolnierkiewicz 2019-06-07 735 .fb_blank = pvr2fb_blank,
423273970906070 drivers/video/fbdev/pvr2fb.c Thomas Zimmermann 2023-09-27 736 __FB_DEFAULT_IOMEM_OPS_DRAW,
db7f2cb965cb792 drivers/video/fbdev/pvr2fb.c Bartlomiej Zolnierkiewicz 2019-06-07 737 .fb_check_var = pvr2fb_check_var,
db7f2cb965cb792 drivers/video/fbdev/pvr2fb.c Bartlomiej Zolnierkiewicz 2019-06-07 738 .fb_set_par = pvr2fb_set_par,
423273970906070 drivers/video/fbdev/pvr2fb.c Thomas Zimmermann 2023-09-27 739 __FB_DEFAULT_IOMEM_OPS_MMAP,
db7f2cb965cb792 drivers/video/fbdev/pvr2fb.c Bartlomiej Zolnierkiewicz 2019-06-07 740 };
db7f2cb965cb792 drivers/video/fbdev/pvr2fb.c Bartlomiej Zolnierkiewicz 2019-06-07 741
:::::: The code at line 730 was first introduced by commit
:::::: 4232739709060703e9dd6f5d6839c37e008d389d fbdev/pvr2fb: Initialize fb_ops to fbdev I/O-memory helpers
:::::: TO: Thomas Zimmermann <tzimmermann@suse.de>
:::::: CC: Thomas Zimmermann <tzimmermann@suse.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-13 5:21 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=202607131247.fpQ6eTc7-lkp@intel.com \
--to=lkp@intel.com \
--cc=deller@gmx.de \
--cc=fuchsfl@gmail.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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