From: kernel test robot <lkp@intel.com>
To: Ben Skeggs <bskeggs@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Danilo Krummrich <dakr@kernel.org>
Subject: drivers/gpu/drm/nouveau/nv10_fence.c:35:40: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Mon, 15 Dec 2025 01:48:43 +0800 [thread overview]
Message-ID: <202512150150.LLdn83bp-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
commit: 0df26c0d69dce1141218e0e5ed0ad378a0c6c058 drm/nouveau: remove push pointer from nouveau_channel
date: 1 year, 5 months ago
config: powerpc64-randconfig-r112-20251212 (https://download.01.org/0day-ci/archive/20251215/202512150150.LLdn83bp-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251215/202512150150.LLdn83bp-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/202512150150.LLdn83bp-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 *
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:[~2025-12-14 17:49 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=202512150150.LLdn83bp-lkp@intel.com \
--to=lkp@intel.com \
--cc=bskeggs@nvidia.com \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.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 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.