From: kernel test robot <lkp@intel.com>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
WANG Xuerui <git@xen0n.name>, Jianmin Lv <lvjianmin@loongson.cn>
Subject: drivers/infiniband/hw/vmw_pvrdma/pvrdma.h:311:16: sparse: sparse: incorrect type in argument 1 (different base types)
Date: Fri, 11 Aug 2023 01:01:25 +0800 [thread overview]
Message-ID: <202308110052.GRrF9sM5-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 374a7f47bf401441edff0a64465e61326bf70a82
commit: 57fc7323a8e7c2e7c1d5795ab63cb3ffea3cfdfb LoongArch: Add PCI controller support
date: 12 months ago
config: loongarch-randconfig-r091-20230810 (https://download.01.org/0day-ci/archive/20230811/202308110052.GRrF9sM5-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230811/202308110052.GRrF9sM5-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/202308110052.GRrF9sM5-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/infiniband/hw/vmw_pvrdma/pvrdma_cq.c: note: in included file:
>> drivers/infiniband/hw/vmw_pvrdma/pvrdma.h:311:16: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int [usertype] value @@ got restricted __le32 [usertype] @@
drivers/infiniband/hw/vmw_pvrdma/pvrdma.h:311:16: sparse: expected unsigned int [usertype] value
drivers/infiniband/hw/vmw_pvrdma/pvrdma.h:311:16: sparse: got restricted __le32 [usertype]
>> drivers/infiniband/hw/vmw_pvrdma/pvrdma.h:311:16: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int [usertype] value @@ got restricted __le32 [usertype] @@
drivers/infiniband/hw/vmw_pvrdma/pvrdma.h:311:16: sparse: expected unsigned int [usertype] value
drivers/infiniband/hw/vmw_pvrdma/pvrdma.h:311:16: sparse: got restricted __le32 [usertype]
vim +311 drivers/infiniband/hw/vmw_pvrdma/pvrdma.h
29c8d9eba550c6 Adit Ranadive 2016-10-02 308
29c8d9eba550c6 Adit Ranadive 2016-10-02 309 static inline void pvrdma_write_uar_cq(struct pvrdma_dev *dev, u32 val)
29c8d9eba550c6 Adit Ranadive 2016-10-02 310 {
29c8d9eba550c6 Adit Ranadive 2016-10-02 @311 writel(cpu_to_le32(val), dev->driver_uar.map + PVRDMA_UAR_CQ_OFFSET);
29c8d9eba550c6 Adit Ranadive 2016-10-02 312 }
29c8d9eba550c6 Adit Ranadive 2016-10-02 313
:::::: The code at line 311 was first introduced by commit
:::::: 29c8d9eba550c6d73d17cc1618a9f5f2a7345aa1 IB: Add vmw_pvrdma driver
:::::: TO: Adit Ranadive <aditr@vmware.com>
:::::: CC: Doug Ledford <dledford@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-10 17:03 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=202308110052.GRrF9sM5-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenhuacai@loongson.cn \
--cc=git@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
--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®