From: kernel test robot <lkp@intel.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: include/linux/device.h:381:23: sparse: sparse: incorrect type in return expression (different address spaces)
Date: Thu, 7 Nov 2024 13:45:59 +0800 [thread overview]
Message-ID: <202411071306.NRIW9j4f-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ff7afaeca1a15fbeaa2c4795ee806c0667bd77b2
commit: f6bb3e9d98c2e8d70587d5ddaf9426ef30d7865c net: pcs: xpcs: Add Synopsys DW xPCS platform device driver
date: 4 months ago
config: s390-randconfig-r121-20241106 (https://download.01.org/0day-ci/archive/20241107/202411071306.NRIW9j4f-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
reproduce: (https://download.01.org/0day-ci/archive/20241107/202411071306.NRIW9j4f-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/202411071306.NRIW9j4f-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/net/pcs/pcs-xpcs-plat.c: note: in included file:
>> include/linux/device.h:381:23: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected void [noderef] __iomem * @@ got void * @@
include/linux/device.h:381:23: sparse: expected void [noderef] __iomem *
include/linux/device.h:381:23: sparse: got void *
vim +381 include/linux/device.h
da7c07b1083809 Mark Brown 2023-07-18 376
da7c07b1083809 Mark Brown 2023-07-18 377 static inline
da7c07b1083809 Mark Brown 2023-07-18 378 void __iomem *devm_ioremap_resource(struct device *dev,
da7c07b1083809 Mark Brown 2023-07-18 379 const struct resource *res)
da7c07b1083809 Mark Brown 2023-07-18 380 {
da7c07b1083809 Mark Brown 2023-07-18 @381 return ERR_PTR(-EINVAL);
da7c07b1083809 Mark Brown 2023-07-18 382 }
da7c07b1083809 Mark Brown 2023-07-18 383
:::::: The code at line 381 was first introduced by commit
:::::: da7c07b1083809888c82522e74370f962fb7685e driver core: Provide stubs for !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:[~2024-11-07 5:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 5:45 kernel test robot [this message]
2024-11-26 11:34 kernel test robot
2025-01-22 6:46 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=202411071306.NRIW9j4f-lkp@intel.com \
--to=lkp@intel.com \
--cc=fancer.lancer@gmail.com \
--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
all inboxes | Powered by JetHome®