From: kernel test robot <lkp@intel.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: drivers/edac/i10nm_base.c:149:19: sparse: sparse: cast removes address space '__iomem' of expression
Date: Sat, 18 Jul 2020 12:13:11 +0800 [thread overview]
Message-ID: <202007181205.NWL36a5v%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2221 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4ebf8d7649cd86c41c41bf48da4b7761da2d5009
commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to define address spaces
date: 4 weeks ago
config: x86_64-randconfig-s021-20200718 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.2-49-g707c5017-dirty
git checkout 670d0a4b10704667765f7d18f7592993d02783aa
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
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/edac/i10nm_base.c:149:19: sparse: sparse: cast removes address space '__iomem' of expression
drivers/edac/i10nm_base.c:170:31: sparse: sparse: cast removes address space '__iomem' of expression
drivers/edac/i10nm_base.c:171:37: sparse: sparse: cast removes address space '__iomem' of expression
vim +/__iomem +149 drivers/edac/i10nm_base.c
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 144
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 145 static bool i10nm_check_ecc(struct skx_imc *imc, int chan)
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 146 {
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 147 u32 mcmtr;
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 148
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 @149 mcmtr = *(u32 *)(imc->mbase + 0x20ef8 + chan * 0x4000);
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 150 edac_dbg(1, "ch%d mcmtr reg %x\n", chan, mcmtr);
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 151
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 152 return !!GET_BITFIELD(mcmtr, 2, 2);
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 153 }
d4dc89d069aab9 Qiuxu Zhuo 2019-01-30 154
:::::: The code at line 149 was first introduced by commit
:::::: d4dc89d069aab9074e2493a4c2f3969a0a0b91c1 EDAC, i10nm: Add a driver for Intel 10nm server processors
:::::: TO: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
:::::: CC: Borislav Petkov <bp@suse.de>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33610 bytes --]
reply other threads:[~2020-07-18 4:14 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=202007181205.NWL36a5v%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/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®