From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: include/linux/platform_device.h:91:23: sparse: sparse: incorrect type in return expression (different address spaces)
Date: Fri, 17 Nov 2023 09:15:04 +0800 [thread overview]
Message-ID: <202311170948.rDwaXfji-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "only kconfig file changed"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Mark Brown <broonie@kernel.org>
CC: Takashi Iwai <tiwai@suse.de>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 7475e51b87969e01a6812eac713a1c8310372e8a
commit: 512d092d78823f9813f4af38090b33c454137a4c ALSA: Enable build with UML
date: 4 months ago
:::::: branch date: 12 hours ago
:::::: commit date: 4 months ago
config: um-randconfig-r122-20231117 (https://download.01.org/0day-ci/archive/20231117/202311170948.rDwaXfji-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231117/202311170948.rDwaXfji-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/r/202311170948.rDwaXfji-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
sound/soc/codecs/inno_rk3036.c: note: in included file (through include/sound/soc.h):
>> include/linux/platform_device.h:91:23: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] __iomem * @@ got void * @@
include/linux/platform_device.h:91:23: sparse: expected void [noderef] __iomem *
include/linux/platform_device.h:91:23: sparse: got void *
--
sound/soc/codecs/msm8916-wcd-digital.c: note: in included file:
>> include/linux/platform_device.h:91:23: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] __iomem * @@ got void * @@
include/linux/platform_device.h:91:23: sparse: expected void [noderef] __iomem *
include/linux/platform_device.h:91:23: sparse: got void *
--
sound/soc/codecs/rk3328_codec.c: note: in included file:
>> include/linux/platform_device.h:91:23: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] __iomem * @@ got void * @@
include/linux/platform_device.h:91:23: sparse: expected void [noderef] __iomem *
include/linux/platform_device.h:91:23: sparse: got void *
--
sound/soc/codecs/lpass-wsa-macro.c: note: in included file:
>> include/linux/platform_device.h:91:23: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] __iomem * @@ got void * @@
include/linux/platform_device.h:91:23: sparse: expected void [noderef] __iomem *
include/linux/platform_device.h:91:23: sparse: got void *
--
sound/soc/codecs/lpass-va-macro.c: note: in included file (through include/linux/of_device.h, include/linux/of_platform.h):
>> include/linux/platform_device.h:91:23: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] __iomem * @@ got void * @@
include/linux/platform_device.h:91:23: sparse: expected void [noderef] __iomem *
include/linux/platform_device.h:91:23: sparse: got void *
--
sound/soc/codecs/lpass-rx-macro.c: note: in included file:
>> include/linux/platform_device.h:91:23: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] __iomem * @@ got void * @@
include/linux/platform_device.h:91:23: sparse: expected void [noderef] __iomem *
include/linux/platform_device.h:91:23: sparse: got void *
vim +91 include/linux/platform_device.h
a0c74f6c9ea9ce Mark Brown 2023-07-18 85
a0c74f6c9ea9ce Mark Brown 2023-07-18 86
a0c74f6c9ea9ce Mark Brown 2023-07-18 87 static inline void __iomem *
a0c74f6c9ea9ce Mark Brown 2023-07-18 88 devm_platform_ioremap_resource(struct platform_device *pdev,
a0c74f6c9ea9ce Mark Brown 2023-07-18 89 unsigned int index)
a0c74f6c9ea9ce Mark Brown 2023-07-18 90 {
a0c74f6c9ea9ce Mark Brown 2023-07-18 @91 return ERR_PTR(-EINVAL);
a0c74f6c9ea9ce Mark Brown 2023-07-18 92 }
a0c74f6c9ea9ce Mark Brown 2023-07-18 93
:::::: The code at line 91 was first introduced by commit
:::::: a0c74f6c9ea9cebd7a8f38142bf87e7c12c2905d platform: Provide stubs for !HAS_IOMEM builds
:::::: TO: Mark Brown <broonie@kernel.org>
:::::: CC: Mark Brown <broonie@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-17 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 1:15 kernel test robot [this message]
2023-11-17 8:35 ` include/linux/platform_device.h:91:23: sparse: sparse: incorrect type in return expression (different address spaces) Liu, Yujie
2023-12-11 9:18 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=202311170948.rDwaXfji-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 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.