From: kernel test robot <lkp@intel.com>
To: Ben Skeggs <bskeggs@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Danilo Krummrich <dakr@kernel.org>
Subject: [linux-next:master 1060/2655] drivers/gpu/drm/nouveau/nv10_fence.c:35:40: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Thu, 1 Aug 2024 18:02:59 +0800 [thread overview]
Message-ID: <202408011836.hAzQyIkl-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 048d8cb65cde9fe7534eb4440bcfddcf406bb49c
commit: 0df26c0d69dce1141218e0e5ed0ad378a0c6c058 [1060/2655] drm/nouveau: remove push pointer from nouveau_channel
config: x86_64-randconfig-122-20240801 (https://download.01.org/0day-ci/archive/20240801/202408011836.hAzQyIkl-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240801/202408011836.hAzQyIkl-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/202408011836.hAzQyIkl-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/nouveau/nv10_fence.c:35:40: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct nvif_push *push @@ got struct nvif_push [noderef] __rcu * @@
drivers/gpu/drm/nouveau/nv10_fence.c:35:40: sparse: expected struct nvif_push *push
drivers/gpu/drm/nouveau/nv10_fence.c:35:40: sparse: got struct nvif_push [noderef] __rcu *
drivers/gpu/drm/nouveau/nv10_fence.c:38:17: sparse: sparse: cast removes address space '__iomem' of expression
drivers/gpu/drm/nouveau/nv10_fence.c:38:17: sparse: sparse: cast removes address space '__iomem' of expression
vim +35 drivers/gpu/drm/nouveau/nv10_fence.c
31
32 int
33 nv10_fence_emit(struct nouveau_fence *fence)
34 {
> 35 struct nvif_push *push = &fence->channel->chan.push;
36 int ret = PUSH_WAIT(push, 2);
37 if (ret == 0) {
38 PUSH_MTHD(push, NV06E, SET_REFERENCE, fence->base.seqno);
39 PUSH_KICK(push);
40 }
41 return ret;
42 }
43
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-01 10: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=202408011836.hAzQyIkl-lkp@intel.com \
--to=lkp@intel.com \
--cc=bskeggs@nvidia.com \
--cc=dakr@kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).