From: kernel test robot <lkp@intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
thomas.hellstrom@linux.intel.com, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, matthew.brost@intel.com,
matthew.auld@intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 4/6] drm/ttm: rename ttm_bo_put to _fini
Date: Tue, 17 Jun 2025 10:08:17 +0800 [thread overview]
Message-ID: <202506170945.w3e0EBJ6-lkp@intel.com> (raw)
In-Reply-To: <20250616130726.22863-4-christian.koenig@amd.com>
Hi Christian,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on next-20250616]
[cannot apply to drm-xe/drm-xe-next drm-exynos/exynos-drm-next linus/master drm/drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip v6.16-rc2]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Christian-K-nig/drm-xe-stop-asserting-on-the-TTM-refcount/20250616-210818
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20250616130726.22863-4-christian.koenig%40amd.com
patch subject: [PATCH 4/6] drm/ttm: rename ttm_bo_put to _fini
config: riscv-randconfig-002-20250617 (https://download.01.org/0day-ci/archive/20250617/202506170945.w3e0EBJ6-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250617/202506170945.w3e0EBJ6-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/202506170945.w3e0EBJ6-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/nouveau/nouveau_dma.h:30,
from drivers/gpu/drm/nouveau/nouveau_chan.c:31:
drivers/gpu/drm/nouveau/nouveau_bo.h: In function 'nouveau_bo_fini':
>> drivers/gpu/drm/nouveau/nouveau_bo.h:60:2: error: implicit declaration of function 'ttm_bo_put'; did you mean 'ttm_bo_pin'? [-Werror=implicit-function-declaration]
60 | ttm_bo_put(&bo->bo);
| ^~~~~~~~~~
| ttm_bo_pin
cc1: some warnings being treated as errors
vim +60 drivers/gpu/drm/nouveau/nouveau_bo.h
8be21a6402baa5 Ben Skeggs 2012-07-18 56
bf32a3a1268638 Danilo Krummrich 2024-07-18 57 static inline void
bf32a3a1268638 Danilo Krummrich 2024-07-18 58 nouveau_bo_fini(struct nouveau_bo *bo)
8be21a6402baa5 Ben Skeggs 2012-07-18 59 {
bf32a3a1268638 Danilo Krummrich 2024-07-18 @60 ttm_bo_put(&bo->bo);
8be21a6402baa5 Ben Skeggs 2012-07-18 61 }
8be21a6402baa5 Ben Skeggs 2012-07-18 62
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-17 2:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 13:07 [PATCH 1/6] drm/vmwgfx: drop printing the TTM refcount for debugging Christian König
2025-06-16 13:07 ` [PATCH 2/6] drm/xe: stop asserting on the TTM refcount Christian König
2025-06-23 14:54 ` Matthew Brost
2025-06-16 13:07 ` [PATCH 3/6] drm/ttm: fix error handling in ttm_buffer_object_transfer Christian König
2025-06-24 2:24 ` Matthew Brost
2025-06-16 13:07 ` [PATCH 4/6] drm/ttm: rename ttm_bo_put to _fini Christian König
2025-06-17 2:08 ` kernel test robot [this message]
2025-06-16 13:07 ` [PATCH 5/6] drm/ttm: disable ttm_bo_validate_deleted_evict for now Christian König
2025-06-16 13:07 ` [PATCH 6/6] drm/ttm: replace TTMs refcount with the DRM refcount Christian König
2025-06-17 4:27 ` kernel test robot
2025-06-17 10:18 ` Thomas Hellström
2025-06-16 14:23 ` ✗ LGCI.VerificationFailed: failure for series starting with [1/6] drm/vmwgfx: drop printing the TTM refcount for debugging Patchwork
2025-06-23 9:35 ` ✗ CI.checkpatch: warning for series starting with [1/6] drm/vmwgfx: drop printing the TTM refcount for debugging (rev2) Patchwork
2025-06-23 9:36 ` ✗ CI.KUnit: failure " Patchwork
2025-06-23 19:02 ` [PATCH 1/6] drm/vmwgfx: drop printing the TTM refcount for debugging Ian Forbes
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=202506170945.w3e0EBJ6-lkp@intel.com \
--to=lkp@intel.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.hellstrom@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox