From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [intel-linux-intel-lts:5.4/yocto 72/1142] drivers/gpu/drm/kmb/kmb_drv.c:99:31: sparse: sparse: incorrect type in return expression (different address spaces)
Date: Wed, 03 Feb 2021 08:27:06 +0800 [thread overview]
Message-ID: <202102030803.RRZjuCLN-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3252 bytes --]
tree: https://github.com/intel/linux-intel-lts.git 5.4/yocto
head: eeb611e5394c56d45c5cc8f7dc484c9f19e93143
commit: d855ca729624b25fa0552c548f8805b63bb0c017 [72/1142] drm/kmb: Cleanup probe functions
config: arm64-randconfig-s031-20210202 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.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.3-215-g0fb77bb6-dirty
# https://github.com/intel/linux-intel-lts/commit/d855ca729624b25fa0552c548f8805b63bb0c017
git remote add intel-linux-intel-lts https://github.com/intel/linux-intel-lts.git
git fetch --no-tags intel-linux-intel-lts 5.4/yocto
git checkout d855ca729624b25fa0552c548f8805b63bb0c017
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
>> drivers/gpu/drm/kmb/kmb_drv.c:99:31: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] <asn:2> * @@ got void * @@
drivers/gpu/drm/kmb/kmb_drv.c:99:31: sparse: expected void [noderef] <asn:2> *
drivers/gpu/drm/kmb/kmb_drv.c:99:31: sparse: got void *
drivers/gpu/drm/kmb/kmb_drv.c:104:31: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] <asn:2> * @@ got void * @@
drivers/gpu/drm/kmb/kmb_drv.c:104:31: sparse: expected void [noderef] <asn:2> *
drivers/gpu/drm/kmb/kmb_drv.c:104:31: sparse: got void *
drivers/gpu/drm/kmb/kmb_drv.c:110:31: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] <asn:2> * @@ got void * @@
drivers/gpu/drm/kmb/kmb_drv.c:110:31: sparse: expected void [noderef] <asn:2> *
drivers/gpu/drm/kmb/kmb_drv.c:110:31: sparse: got void *
vim +99 drivers/gpu/drm/kmb/kmb_drv.c
89
90 static void __iomem *kmb_map_mmio(struct platform_device *pdev, char *name)
91 {
92 struct resource *res;
93 u32 size;
94 void __iomem *mem;
95
96 res = platform_get_resource_byname(pdev, IORESOURCE_MEM, name);
97 if (!res) {
98 DRM_ERROR("failed to get resource for %s\n", name);
> 99 return ERR_PTR(-ENOMEM);
100 }
101 size = resource_size(res);
102 if (!request_mem_region(res->start, size, name)) {
103 DRM_ERROR("failed to reserve %s registers\n", name);
104 return ERR_PTR(-ENOMEM);
105 }
106 mem = ioremap_nocache(res->start, size);
107 if (!mem) {
108 DRM_ERROR("failed to ioremap %s registers\n", name);
109 release_mem_region(res->start, size);
110 return ERR_PTR(-ENOMEM);
111 }
112 return mem;
113 }
114
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 31324 bytes --]
next reply other threads:[~2021-02-03 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 0:27 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-01 0:01 [intel-linux-intel-lts:5.4/yocto 72/1142] drivers/gpu/drm/kmb/kmb_drv.c:99:31: sparse: sparse: incorrect type in return expression (different address spaces) kernel test robot
2020-08-25 10:41 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=202102030803.RRZjuCLN-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.