From: kernel test robot <lkp@intel.com>
To: Michael Kelley <mhklinux@outlook.com>
Cc: oe-kbuild-all@lists.linux.dev, Wei Liu <wei.liu@kernel.org>,
Saurabh Sengar <ssengar@linux.microsoft.com>
Subject: [linux-next:master 3083/3437] drivers/video/fbdev/hyperv_fb.c:1083:28: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Fri, 14 Feb 2025 15:17:52 +0800 [thread overview]
Message-ID: <202502141545.Vrmh7ZlT-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 7b7a883c7f4de1ee5040bd1c32aabaafde54d209
commit: 2a1852f9062bcda671a85dfde52b870fd4122a36 [3083/3437] fbdev: hyperv_fb: iounmap() the correct memory when removing a device
config: i386-randconfig-r123-20250214 (https://download.01.org/0day-ci/archive/20250214/202502141545.Vrmh7ZlT-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250214/202502141545.Vrmh7ZlT-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/202502141545.Vrmh7ZlT-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/video/fbdev/hyperv_fb.c:1006:43: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected char [noderef] __iomem *screen_base @@ got unsigned char *mmio_vp @@
drivers/video/fbdev/hyperv_fb.c:1006:43: sparse: expected char [noderef] __iomem *screen_base
drivers/video/fbdev/hyperv_fb.c:1006:43: sparse: got unsigned char *mmio_vp
drivers/video/fbdev/hyperv_fb.c:1046:25: sparse: sparse: cast removes address space '__iomem' of expression
drivers/video/fbdev/hyperv_fb.c:1050:27: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected char [noderef] __iomem *screen_base @@ got unsigned char *dio_vp @@
drivers/video/fbdev/hyperv_fb.c:1050:27: sparse: expected char [noderef] __iomem *screen_base
drivers/video/fbdev/hyperv_fb.c:1050:27: sparse: got unsigned char *dio_vp
>> drivers/video/fbdev/hyperv_fb.c:1083:28: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got unsigned char *mmio_vp @@
drivers/video/fbdev/hyperv_fb.c:1083:28: sparse: expected void volatile [noderef] __iomem *addr
drivers/video/fbdev/hyperv_fb.c:1083:28: sparse: got unsigned char *mmio_vp
vim +1083 drivers/video/fbdev/hyperv_fb.c
1075
1076 /* Release the framebuffer */
1077 static void hvfb_putmem(struct hv_device *hdev, struct fb_info *info)
1078 {
1079 struct hvfb_par *par = info->par;
1080
1081 if (par->need_docopy) {
1082 vfree(par->dio_vp);
> 1083 iounmap(par->mmio_vp);
1084 vmbus_free_mmio(par->mem->start, screen_fb_size);
1085 } else {
1086 hvfb_release_phymem(hdev, info->fix.smem_start,
1087 screen_fb_size);
1088 }
1089
1090 par->mem = NULL;
1091 }
1092
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-14 7:18 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=202502141545.Vrmh7ZlT-lkp@intel.com \
--to=lkp@intel.com \
--cc=mhklinux@outlook.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.