From: kernel test robot <lkp@intel.com>
To: Andrew Davis <afd@ti.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: include/linux/platform_device.h:91:23: sparse: sparse: incorrect type in return expression (different address spaces)
Date: Sat, 14 Jun 2025 15:36:19 +0800 [thread overview]
Message-ID: <202506141507.mLBNmMsd-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4774cfe3543abb8ee98089f535e28ebfd45b975a
commit: 61de83fd8256e185588670d3cf0bccc3e913819c mux: mmio: Do not use syscon helper to build regmap
date: 6 weeks ago
config: s390-randconfig-r112-20250614 (https://download.01.org/0day-ci/archive/20250614/202506141507.mLBNmMsd-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 8.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250614/202506141507.mLBNmMsd-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/202506141507.mLBNmMsd-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/mux/mmio.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
a0c74f6c9ea9ceb Mark Brown 2023-07-18 85
a0c74f6c9ea9ceb Mark Brown 2023-07-18 86
a0c74f6c9ea9ceb Mark Brown 2023-07-18 87 static inline void __iomem *
a0c74f6c9ea9ceb Mark Brown 2023-07-18 88 devm_platform_ioremap_resource(struct platform_device *pdev,
a0c74f6c9ea9ceb Mark Brown 2023-07-18 89 unsigned int index)
a0c74f6c9ea9ceb Mark Brown 2023-07-18 90 {
a0c74f6c9ea9ceb Mark Brown 2023-07-18 @91 return ERR_PTR(-EINVAL);
a0c74f6c9ea9ceb Mark Brown 2023-07-18 92 }
a0c74f6c9ea9ceb 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:[~2025-06-14 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 7:36 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-05 19:19 include/linux/platform_device.h:91:23: sparse: sparse: incorrect type in return expression (different address spaces) kernel test robot
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=202506141507.mLBNmMsd-lkp@intel.com \
--to=lkp@intel.com \
--cc=afd@ti.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).