From: kernel test robot <lkp@intel.com>
To: Riana Tauro <riana.tauro@intel.com>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev,
aravind.iddamsetty@linux.intel.com, anshuman.gupta@intel.com,
rodrigo.vivi@intel.com, joonas.lahtinen@linux.intel.com,
lukas@wunner.de, simona.vetter@ffwll.ch, airlied@gmail.com,
lucas.demarchi@intel.com, Riana Tauro <riana.tauro@intel.com>,
Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Subject: Re: [PATCH v2 3/4] drm/xe/xe_hw_error: Add support for GT hardware errors
Date: Thu, 27 Nov 2025 13:28:16 +0800 [thread overview]
Message-ID: <202511271357.7pA8zqx0-lkp@intel.com> (raw)
In-Reply-To: <20251126143652.2843242-9-riana.tauro@intel.com>
Hi Riana,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on drm/drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip linus/master drm-exynos/exynos-drm-next v6.18-rc7 next-20251127]
[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/Riana-Tauro/drm-ras-Introduce-the-DRM-RAS-infrastructure-over-generic-netlink/20251126-220942
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20251126143652.2843242-9-riana.tauro%40intel.com
patch subject: [PATCH v2 3/4] drm/xe/xe_hw_error: Add support for GT hardware errors
config: riscv-randconfig-r061-20251127 (https://download.01.org/0day-ci/archive/20251127/202511271357.7pA8zqx0-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251127/202511271357.7pA8zqx0-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/202511271357.7pA8zqx0-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/riscv/include/asm/bitops.h:19,
from include/linux/bitops.h:67,
from include/linux/thread_info.h:27,
from include/asm-generic/preempt.h:5,
from ./arch/riscv/include/generated/asm/preempt.h:1,
from include/linux/preempt.h:79,
from include/linux/spinlock.h:56,
from include/linux/kref.h:16,
from include/linux/configfs.h:25,
from include/linux/fault-inject.h:14,
from drivers/gpu/drm/xe/xe_hw_error.c:6:
>> include/asm-generic/bitops/__ffs.h:45:21: error: nonconstant array index in initializer
45 | #define __ffs(word) generic___ffs(word)
| ^~~~~~~~~~~~~
drivers/gpu/drm/xe/xe_hw_error.c:31:10: note: in expansion of macro '__ffs'
31 | [__ffs(_bit)] = index
| ^~~~~
drivers/gpu/drm/xe/xe_hw_error.c:34:9: note: in expansion of macro 'ERR_INDEX'
34 | ERR_INDEX(XE_GT_ERROR, DRM_XE_GENL_CORE_COMPUTE),
| ^~~~~~~~~
include/asm-generic/bitops/__ffs.h:45:21: note: (near initialization for 'xe_hw_error_map')
45 | #define __ffs(word) generic___ffs(word)
| ^~~~~~~~~~~~~
drivers/gpu/drm/xe/xe_hw_error.c:31:10: note: in expansion of macro '__ffs'
31 | [__ffs(_bit)] = index
| ^~~~~
drivers/gpu/drm/xe/xe_hw_error.c:34:9: note: in expansion of macro 'ERR_INDEX'
34 | ERR_INDEX(XE_GT_ERROR, DRM_XE_GENL_CORE_COMPUTE),
| ^~~~~~~~~
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for ARCH_HAS_ELF_CORE_EFLAGS
Depends on [n]: BINFMT_ELF [=y] && ELF_CORE [=n]
Selected by [y]:
- RISCV [=y]
vim +45 include/asm-generic/bitops/__ffs.h
c1226a005ec400 Akinobu Mita 2006-03-26 43
cb4ede926134a6 Xiao Wang 2023-11-12 44 #ifndef __HAVE_ARCH___FFS
cb4ede926134a6 Xiao Wang 2023-11-12 @45 #define __ffs(word) generic___ffs(word)
cb4ede926134a6 Xiao Wang 2023-11-12 46 #endif
cb4ede926134a6 Xiao Wang 2023-11-12 47
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-27 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 14:36 [PATCH v2 0/4] Introduce DRM_RAS using generic netlink for RAS Riana Tauro
2025-11-26 14:31 ` ✗ CI.checkpatch: warning for Introduce DRM_RAS using generic netlink for RAS (rev2) Patchwork
2025-11-26 14:33 ` ✓ CI.KUnit: success " Patchwork
2025-11-26 14:36 ` [PATCH v2 1/4] drm/ras: Introduce the DRM RAS infrastructure over generic netlink Riana Tauro
2025-11-26 14:36 ` [PATCH v2 2/4] drm/xe/xe_drm_ras: Add support for drm ras Riana Tauro
2025-11-26 18:48 ` Rodrigo Vivi
2025-12-02 3:27 ` Riana Tauro
2025-11-26 14:36 ` [PATCH v2 3/4] drm/xe/xe_hw_error: Add support for GT hardware errors Riana Tauro
2025-11-27 5:28 ` kernel test robot [this message]
2025-11-26 14:36 ` [PATCH v2 4/4] drm/xe/xe_hw_error: Add support for PVC SOC errors Riana Tauro
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=202511271357.7pA8zqx0-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=lukas@wunner.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
/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