From: kernel test robot <lkp@intel.com>
To: Suren Baghdasaryan <surenb@google.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>
Subject: drivers/video/fbdev/pxafb.c:913:24: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Thu, 27 Feb 2025 07:30:54 +0800 [thread overview]
Message-ID: <202502270742.weTnX9Oe-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f4ce1f3318ad4bc12463698696ebc36b145a6aa3
commit: 07438779313caafe52ac1a1a6958d735a5938988 alloc_tag: avoid current->alloc_tag manipulations when profiling is disabled
date: 5 weeks ago
config: arm-randconfig-r132-20250227 (https://download.01.org/0day-ci/archive/20250227/202502270742.weTnX9Oe-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250227/202502270742.weTnX9Oe-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/202502270742.weTnX9Oe-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/video/fbdev/pxafb.c:913:24: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __iomem *video_mem @@ got void *[assigned] _res @@
drivers/video/fbdev/pxafb.c:913:24: sparse: expected void [noderef] __iomem *video_mem
drivers/video/fbdev/pxafb.c:913:24: sparse: got void *[assigned] _res
drivers/video/fbdev/pxafb.c:918:47: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile *x @@ got void [noderef] __iomem *video_mem @@
drivers/video/fbdev/pxafb.c:918:47: sparse: expected void const volatile *x
drivers/video/fbdev/pxafb.c:918:47: sparse: got void [noderef] __iomem *video_mem
drivers/video/fbdev/pxafb.c:974:53: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *virt @@ got void [noderef] __iomem *video_mem @@
drivers/video/fbdev/pxafb.c:974:53: sparse: expected void *virt
drivers/video/fbdev/pxafb.c:974:53: sparse: got void [noderef] __iomem *video_mem
drivers/video/fbdev/pxafb.c:1711:24: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __iomem *video_mem @@ got void *[assigned] _res @@
drivers/video/fbdev/pxafb.c:1711:24: sparse: expected void [noderef] __iomem *video_mem
drivers/video/fbdev/pxafb.c:1711:24: sparse: got void *[assigned] _res
drivers/video/fbdev/pxafb.c:1715:47: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile *x @@ got void [noderef] __iomem *video_mem @@
drivers/video/fbdev/pxafb.c:1715:47: sparse: expected void const volatile *x
drivers/video/fbdev/pxafb.c:1715:47: sparse: got void [noderef] __iomem *video_mem
drivers/video/fbdev/pxafb.c:2387:29: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *virt @@ got void [noderef] __iomem *video_mem @@
drivers/video/fbdev/pxafb.c:2387:29: sparse: expected void *virt
drivers/video/fbdev/pxafb.c:2387:29: sparse: got void [noderef] __iomem *video_mem
drivers/video/fbdev/pxafb.c:2414:29: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *virt @@ got void [noderef] __iomem *video_mem @@
drivers/video/fbdev/pxafb.c:2414:29: sparse: expected void *virt
drivers/video/fbdev/pxafb.c:2414:29: sparse: got void [noderef] __iomem *video_mem
vim +913 drivers/video/fbdev/pxafb.c
782385ae176b30 drivers/video/pxafb.c Eric Miao 2009-03-19 906
48c68c4f1b5424 drivers/video/pxafb.c Greg Kroah-Hartman 2012-12-21 907 static int pxafb_overlay_map_video_memory(struct pxafb_info *pxafb,
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 908 struct pxafb_layer *ofb)
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 909 {
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 910 /* We assume that user will use at most video_mem_size for overlay fb,
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 911 * anyway, it's useless to use 16bpp main plane and 24bpp overlay
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 912 */
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 @913 ofb->video_mem = alloc_pages_exact(PAGE_ALIGN(pxafb->video_mem_size),
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 914 GFP_KERNEL | __GFP_ZERO);
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 915 if (ofb->video_mem == NULL)
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 916 return -ENOMEM;
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 917
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 918 ofb->video_mem_phys = virt_to_phys(ofb->video_mem);
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 919 ofb->video_mem_size = PAGE_ALIGN(pxafb->video_mem_size);
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 920
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 921 mutex_lock(&ofb->fb.mm_lock);
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 922 ofb->fb.fix.smem_start = ofb->video_mem_phys;
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 923 ofb->fb.fix.smem_len = pxafb->video_mem_size;
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 924 mutex_unlock(&ofb->fb.mm_lock);
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 925
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 926 ofb->fb.screen_base = ofb->video_mem;
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 927
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 928 return 0;
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 929 }
1b98d7c4491e5e drivers/video/pxafb.c Vasily Khoruzhick 2011-03-11 930
:::::: The code at line 913 was first introduced by commit
:::::: 1b98d7c4491e5eaba7c403ec1bc5997e6596e569 ARM: pxafb: rework pxafb overlay memory management
:::::: TO: Vasily Khoruzhick <anarsoul@gmail.com>
:::::: CC: Eric Miao <eric.y.miao@gmail.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-26 23:32 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=202502270742.weTnX9Oe-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=surenb@google.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®