From: kernel test robot <lkp@intel.com>
To: steven@liquorix.net
Cc: oe-kbuild-all@lists.linux.dev
Subject: [zen:7.2/vramstuff 9/29] drivers/gpu/drm/ttm/ttm_bo_util.c:52:35: sparse: sparse: symbol 'ttm_transfer_object_funcs' was not declared. Should it be static?
Date: Sun, 30 Aug 2026 18:03:22 +0800 [thread overview]
Message-ID: <202608301731.UpNNN4bY-lkp@intel.com> (raw)
tree: https://github.com/zen-kernel/zen-kernel 7.2/vramstuff
head: 13a8e2000329a36f994acf2fd31d307d27fa9189
commit: 57394df648c83d7fb95565867626ecdda07f4af7 [9/29] drm/ttm: replace TTMs refcount with the DRM refcount v4
config: um-randconfig-r134-20260829 (https://download.01.org/0day-ci/archive/20260830/202608301731.UpNNN4bY-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.4.0-5) 12.4.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260830/202608301731.UpNNN4bY-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/202608301731.UpNNN4bY-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/ttm/ttm_bo_util.c:52:35: sparse: sparse: symbol 'ttm_transfer_object_funcs' was not declared. Should it be static?
drivers/gpu/drm/ttm/ttm_bo_util.c:342:38: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *virtual @@ got void [noderef] __iomem * @@
drivers/gpu/drm/ttm/ttm_bo_util.c:342:38: sparse: expected void *virtual
drivers/gpu/drm/ttm/ttm_bo_util.c:342:38: sparse: got void [noderef] __iomem *
drivers/gpu/drm/ttm/ttm_bo_util.c:348:38: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *virtual @@ got void [noderef] __iomem * @@
drivers/gpu/drm/ttm/ttm_bo_util.c:348:38: sparse: expected void *virtual
drivers/gpu/drm/ttm/ttm_bo_util.c:348:38: sparse: got void [noderef] __iomem *
drivers/gpu/drm/ttm/ttm_bo_util.c:478:28: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got void *virtual @@
drivers/gpu/drm/ttm/ttm_bo_util.c:478:28: sparse: expected void volatile [noderef] __iomem *addr
drivers/gpu/drm/ttm/ttm_bo_util.c:478:28: sparse: got void *virtual
vim +/ttm_transfer_object_funcs +52 drivers/gpu/drm/ttm/ttm_bo_util.c
51
> 52 const struct drm_gem_object_funcs ttm_transfer_object_funcs = {
53 .free = ttm_transfer_object_free,
54 };
55
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-30 10:04 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=202608301731.UpNNN4bY-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=steven@liquorix.net \
/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.