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,
Dave Airlie <airlied@redhat.com>, Timur Tabi <ttabi@nvidia.com>
Subject: drivers/gpu/drm/nouveau/nvif/chanc36f.c:36:9: sparse: sparse: cast removes address space '__iomem' of expression
Date: Thu, 11 Jun 2026 23:33:17 +0800 [thread overview]
Message-ID: <202606112339.qedgsPAM-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 9716c086c8e8b141d35aa61f2e96a2e83de212a7
commit: 862450a85b85a3e88e9065c9d2421f3ef17d054c drm/nouveau/gf100-: track chan progress with non-WFI semaphore release
date: 1 year, 1 month ago
config: powerpc-randconfig-r112-20260611 (https://download.01.org/0day-ci/archive/20260611/202606112339.qedgsPAM-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 16.1.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260611/202606112339.qedgsPAM-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
| Fixes: 862450a85b85 ("drm/nouveau/gf100-: track chan progress with non-WFI semaphore release")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606112339.qedgsPAM-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/nouveau/nvif/chanc36f.c:36:9: sparse: sparse: cast removes address space '__iomem' of expression
>> drivers/gpu/drm/nouveau/nvif/chanc36f.c:36:9: sparse: sparse: cast removes address space '__iomem' of expression
>> drivers/gpu/drm/nouveau/nvif/chanc36f.c:36:9: sparse: sparse: cast removes address space '__iomem' of expression
>> drivers/gpu/drm/nouveau/nvif/chanc36f.c:36:9: sparse: sparse: cast removes address space '__iomem' of expression
drivers/gpu/drm/nouveau/nvif/chanc36f.c:42:9: sparse: sparse: cast removes address space '__iomem' of expression
drivers/gpu/drm/nouveau/nvif/chanc36f.c:42:9: sparse: sparse: cast removes address space '__iomem' of expression
vim +/__iomem +36 drivers/gpu/drm/nouveau/nvif/chanc36f.c
25
26 static int
27 nvif_chanc36f_sem_release(struct nvif_chan *chan, u64 addr, u32 data)
28 {
29 struct nvif_push *push = &chan->push;
30 int ret;
31
32 ret = PUSH_WAIT(push, NVIF_CHANC36F_SEM_RELEASE_SIZE);
33 if (ret)
34 return ret;
35
> 36 PUSH_MTHD(push, NVC36F, SEM_ADDR_LO, lower_32_bits(addr),
37
38 SEM_ADDR_HI, upper_32_bits(addr),
39
40 SEM_PAYLOAD_LO, data);
41
42 PUSH_MTHD(push, NVC36F, SEM_EXECUTE,
43 NVDEF(NVC36F, SEM_EXECUTE, OPERATION, RELEASE) |
44 NVDEF(NVC36F, SEM_EXECUTE, RELEASE_WFI, DIS) |
45 NVDEF(NVC36F, SEM_EXECUTE, PAYLOAD_SIZE, 32BIT) |
46 NVDEF(NVC36F, SEM_EXECUTE, RELEASE_TIMESTAMP, DIS));
47
48 return 0;
49 }
50
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-06-11 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 15:33 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-13 17:12 drivers/gpu/drm/nouveau/nvif/chanc36f.c:36:9: sparse: sparse: cast removes address space '__iomem' of expression kernel test robot
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=202606112339.qedgsPAM-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@redhat.com \
--cc=bskeggs@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ttabi@nvidia.com \
/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.