Hi Thomas, kernel test robot noticed the following build warnings: [auto build test WARNING on drm-xe/drm-xe-next] [also build test WARNING on linus/master v6.12-rc7 next-20241113] [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/Thomas-Hellstr-m/drm-ttm-Balance-ttm_resource_cursor_init-and-ttm_resource_cursor_fini/20241114-023727 base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next patch link: https://lore.kernel.org/r/20241113183550.6228-3-thomas.hellstrom%40linux.intel.com patch subject: [PATCH v13 2/8] drm/ttm: Provide a shmem backup implementation config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20241114/202411140637.T225Mshs-lkp@xxxxxxxxx/config) compiler: s390-linux-gcc (GCC) 14.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241114/202411140637.T225Mshs-lkp@xxxxxxxxx/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@xxxxxxxxx> | Closes: https://lore.kernel.org/oe-kbuild-all/202411140637.T225Mshs-lkp@xxxxxxxxx/ All warnings (new ones prefixed by >>): >> drivers/gpu/drm/ttm/ttm_backup.c:172: warning: expecting prototype for ttm_backup_shmem_bytes_avail(). Prototype was for ttm_backup_bytes_avail() instead vim +172 drivers/gpu/drm/ttm/ttm_backup.c 161 162 /** 163 * ttm_backup_shmem_bytes_avail() - Report the approximate number of bytes of backup space 164 * left for backup. 165 * 166 * This function is intended also for driver use to indicate whether a 167 * backup attempt is meaningful. 168 * 169 * Return: An approximate size of backup space available. 170 */ 171 u64 ttm_backup_bytes_avail(void) > 172 { 173 /* 174 * The idea behind backing up to shmem is that shmem objects may 175 * eventually be swapped out. So no point swapping out if there 176 * is no or low swap-space available. But the accuracy of this 177 * number also depends on shmem actually swapping out backed-up 178 * shmem objects without too much buffering. 179 */ 180 return (u64)get_nr_swap_pages() << PAGE_SHIFT; 181 } 182 EXPORT_SYMBOL_GPL(ttm_backup_bytes_avail); 183 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
