From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jgunthorpe:for_maor_reuse_roce_gid 12/16] drivers/infiniband/core/cache.c:372:27: sparse: sparse: symbol 'get_valid_entry' was not declared. Should it be static?
Date: Sun, 2 Jul 2023 18:32:43 +0800 [thread overview]
Message-ID: <202307021819.6rlwlkIs-lkp@intel.com> (raw)
tree: https://github.com/jgunthorpe/linux for_maor_reuse_roce_gid
head: 1b26be51e181c4a802d87e5d1f806d3722b3a834
commit: 23f090b3a944d84665bfaac23948a0a36a579a7c [12/16] rdma/gidtable: Use an xarray instead of a preallocated array
config: i386-randconfig-i061-20230702 (https://download.01.org/0day-ci/archive/20230702/202307021819.6rlwlkIs-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230702/202307021819.6rlwlkIs-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/202307021819.6rlwlkIs-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/infiniband/core/cache.c:372:27: sparse: sparse: symbol 'get_valid_entry' was not declared. Should it be static?
drivers/infiniband/core/cache.c:666:47: sparse: sparse: incompatible types in comparison expression (different address spaces):
drivers/infiniband/core/cache.c:666:47: sparse: struct net_device [noderef] __rcu *
drivers/infiniband/core/cache.c:666:47: sparse: struct net_device *
drivers/infiniband/core/cache.c:704:43: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct net_device [noderef] __rcu *ndev @@ got struct net_device *ndev @@
drivers/infiniband/core/cache.c:704:43: sparse: expected struct net_device [noderef] __rcu *ndev
drivers/infiniband/core/cache.c:704:43: sparse: got struct net_device *ndev
drivers/infiniband/core/cache.c:864:23: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct net_device [noderef] __rcu *[addressable] ndev @@ got struct net_device *ndev @@
drivers/infiniband/core/cache.c:864:23: sparse: expected struct net_device [noderef] __rcu *[addressable] ndev
drivers/infiniband/core/cache.c:864:23: sparse: got struct net_device *ndev
drivers/infiniband/core/cache.c:1032:52: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct net_device [noderef] __rcu *ndev @@ got struct net_device *ndev @@
drivers/infiniband/core/cache.c:1032:52: sparse: expected struct net_device [noderef] __rcu *ndev
drivers/infiniband/core/cache.c:1032:52: sparse: got struct net_device *ndev
drivers/infiniband/core/cache.c:1443:59: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct net_device *dev @@ got struct net_device [noderef] __rcu *const ndev @@
drivers/infiniband/core/cache.c:1443:59: sparse: expected struct net_device *dev
drivers/infiniband/core/cache.c:1443:59: sparse: got struct net_device [noderef] __rcu *const ndev
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-02 10:33 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=202307021819.6rlwlkIs-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.