Hi Himal, kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-xe/drm-xe-next] [cannot apply to linus/master v6.15-rc1 next-20250407] [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/Himal-Prasad-Ghimiray/drm-xe-Introduce-xe_vma_op_prefetch_range-struct-for-prefetch-of-ranges/20250407-215536 base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next patch link: https://lore.kernel.org/r/20250407101719.3350996-17-himal.prasad.ghimiray%40intel.com patch subject: [PATCH v2 16/32] Introduce drm_gpuvm_sm_map_ops_flags enums for sm_map_ops config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20250408/[email protected]/config) compiler: alpha-linux-gcc (GCC) 14.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250408/[email protected]/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 <[email protected]> | Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/ All warnings (new ones prefixed by >>): >> include/drm/drm_gpuvm.h:233: warning: expecting prototype for enum >> drm_gpuvm_madvise_flags. Prototype was for enum drm_gpuvm_sm_map_ops_flags >> instead vim +233 include/drm/drm_gpuvm.h 213 214 /** 215 * enum drm_gpuvm_madvise_flags - flags for drm_gpuvm split/merge ops 216 */ 217 enum drm_gpuvm_sm_map_ops_flags { 218 /** 219 * @DRM_GPUVM_SM_MAP_NOT_MADVISE: DEFAULT sm_map ops 220 */ 221 DRM_GPUVM_SM_MAP_NOT_MADVISE = 0, 222 223 /** 224 * @DRM_GPUVM_SKIP_GEM_OBJ_VA_SPLIT_MADVISE: This flag is used by 225 * drm_gpuvm_sm_map_ops_create to iterate over GPUVMA's in the 226 * user-provided range and split the existing non-GEM object VMA if the 227 * start or end of the input range lies within it. The operations can 228 * create up to 2 REMAPS and 2 MAPs. Unlike drm_gpuvm_sm_map_ops_flags 229 * in default mode, the operation with this flag will never have UNMAPs and 230 * merges, and can be without any final operations. 231 */ 232 DRM_GPUVM_SKIP_GEM_OBJ_VA_SPLIT_MADVISE = BIT(0), > 233 }; 234 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
