From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 5500/7050] drivers/net/ethernet/marvell/octeontx2/af/rvu.c:722:21: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Sun, 8 Mar 2020 15:30:23 +0800 [thread overview]
Message-ID: <202003081520.wWnUraoG%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b86a6a241b7c60ca7a6ca4fb3c0d2aedbbf2c1b6
commit: 4f4eebf26f0da871fea5b3c489eafce2fbcda8bb [5500/7050] octeontx2-af: Optimize data retrieval from firmware
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-174-g094d5a94-dirty
git checkout 4f4eebf26f0da871fea5b3c489eafce2fbcda8bb
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/net/ethernet/marvell/octeontx2/af/rvu.c:722:21: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct rvu_fwdata *fwdata @@ got void struct rvu_fwdata *fwdata @@
drivers/net/ethernet/marvell/octeontx2/af/rvu.c:722:21: sparse: expected struct rvu_fwdata *fwdata
drivers/net/ethernet/marvell/octeontx2/af/rvu.c:722:21: sparse: got void [noderef] <asn:2> *
>> drivers/net/ethernet/marvell/octeontx2/af/rvu.c:728:28: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] <asn:2> *addr @@ got [noderef] <asn:2> *addr @@
drivers/net/ethernet/marvell/octeontx2/af/rvu.c:728:28: sparse: expected void volatile [noderef] <asn:2> *addr
drivers/net/ethernet/marvell/octeontx2/af/rvu.c:728:28: sparse: got struct rvu_fwdata *fwdata
drivers/net/ethernet/marvell/octeontx2/af/rvu.c:741:28: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] <asn:2> *addr @@ got [noderef] <asn:2> *addr @@
drivers/net/ethernet/marvell/octeontx2/af/rvu.c:741:28: sparse: expected void volatile [noderef] <asn:2> *addr
drivers/net/ethernet/marvell/octeontx2/af/rvu.c:741:28: sparse: got struct rvu_fwdata *fwdata
vim +722 drivers/net/ethernet/marvell/octeontx2/af/rvu.c
712
713 static int rvu_fwdata_init(struct rvu *rvu)
714 {
715 u64 fwdbase;
716 int err;
717
718 /* Get firmware data base address */
719 err = cgx_get_fwdata_base(&fwdbase);
720 if (err)
721 goto fail;
> 722 rvu->fwdata = ioremap_wc(fwdbase, sizeof(struct rvu_fwdata));
723 if (!rvu->fwdata)
724 goto fail;
725 if (!is_rvu_fwdata_valid(rvu)) {
726 dev_err(rvu->dev,
727 "Mismatch in 'fwdata' struct btw kernel and firmware\n");
> 728 iounmap(rvu->fwdata);
729 rvu->fwdata = NULL;
730 return -EINVAL;
731 }
732 return 0;
733 fail:
734 dev_info(rvu->dev, "Unable to fetch 'fwdata' from firmware\n");
735 return -EIO;
736 }
737
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-03-08 7:31 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=202003081520.wWnUraoG%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
/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