From: kernel test robot <lkp@intel.com>
To: Baoquan He <bhe@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Christoph Hellwig <hch@lst.de>,
"Mike Rapoport (IBM)" <rppt@kernel.org>
Subject: drivers/video/fbdev/imsttfb.c:1561:20: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Thu, 30 Nov 2023 20:55:37 +0800 [thread overview]
Message-ID: <202311302054.loV1YuMw-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3b47bc037bd44f142ac09848e8d3ecccc726be99
commit: 426b313f356a314af335899c51250dc0f49cd4a7 parisc: mm: convert to GENERIC_IOREMAP
date: 3 months ago
config: parisc-randconfig-m041-20230821 (https://download.01.org/0day-ci/archive/20231130/202311302054.loV1YuMw-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20231130/202311302054.loV1YuMw-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/202311302054.loV1YuMw-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/video/fbdev/imsttfb.c:1524:30: sparse: sparse: cast removes address space '__iomem' of expression
drivers/video/fbdev/imsttfb.c:1524:27: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected char [noderef] __iomem *screen_base @@ got unsigned char [usertype] * @@
drivers/video/fbdev/imsttfb.c:1524:27: sparse: expected char [noderef] __iomem *screen_base
drivers/video/fbdev/imsttfb.c:1524:27: sparse: got unsigned char [usertype] *
drivers/video/fbdev/imsttfb.c:1533:27: sparse: sparse: cast removes address space '__iomem' of expression
>> drivers/video/fbdev/imsttfb.c:1561:20: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got unsigned char [usertype] *cmap_regs @@
drivers/video/fbdev/imsttfb.c:1561:20: sparse: expected void volatile [noderef] __iomem *addr
drivers/video/fbdev/imsttfb.c:1561:20: sparse: got unsigned char [usertype] *cmap_regs
drivers/video/fbdev/imsttfb.c:1361:15: sparse: sparse: cast removes address space '__iomem' of expression
drivers/video/fbdev/imsttfb.c:1362:16: sparse: sparse: cast removes address space '__iomem' of expression
--
>> drivers/video/fbdev/aty/atyfb_base.c:3734:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got unsigned char [usertype] *addr @@
drivers/video/fbdev/aty/atyfb_base.c:3734:37: sparse: expected void volatile [noderef] __iomem *addr
drivers/video/fbdev/aty/atyfb_base.c:3734:37: sparse: got unsigned char [usertype] *addr
drivers/video/fbdev/aty/atyfb_base.c:1787:15: sparse: sparse: self-comparison always evaluates to false
vim +1561 drivers/video/fbdev/imsttfb.c
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1553
48c68c4f1b5424 drivers/video/imsttfb.c Greg Kroah-Hartman 2012-12-21 1554 static void imsttfb_remove(struct pci_dev *pdev)
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1555 {
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1556 struct fb_info *info = pci_get_drvdata(pdev);
94f9e09ce531d4 drivers/video/imsttfb.c Antonino A. Daplas 2006-01-09 1557 struct imstt_par *par = info->par;
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1558 int size = pci_resource_len(pdev, 0);
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1559
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1560 unregister_framebuffer(info);
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 @1561 iounmap(par->cmap_regs);
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1562 iounmap(par->dc_regs);
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1563 iounmap(info->screen_base);
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1564 release_mem_region(info->fix.smem_start, size);
94f9e09ce531d4 drivers/video/imsttfb.c Antonino A. Daplas 2006-01-09 1565 framebuffer_release(info);
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1566 }
^1da177e4c3f41 drivers/video/imsttfb.c Linus Torvalds 2005-04-16 1567
:::::: The code at line 1561 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/wiki
reply other threads:[~2023-11-30 12:56 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=202311302054.loV1YuMw-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rppt@kernel.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
all inboxes | Powered by JetHome®