From: kernel test robot <lkp@intel.com>
To: Raag Jadav <raag.jadav@intel.com>,
airlied@gmail.com, simona@ffwll.ch, lucas.demarchi@intel.com,
rodrigo.vivi@intel.com, jani.nikula@linux.intel.com,
andriy.shevchenko@linux.intel.com, lina@asahilina.net,
michal.wajdeczko@intel.com, christian.koenig@amd.com
Cc: oe-kbuild-all@lists.linux.dev, intel-xe@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
himal.prasad.ghimiray@intel.com,
aravind.iddamsetty@linux.intel.com, anshuman.gupta@intel.com,
alexander.deucher@amd.com, andrealmeid@igalia.com,
amd-gfx@lists.freedesktop.org, kernel-dev@igalia.com,
Raag Jadav <raag.jadav@intel.com>
Subject: Re: [PATCH v8 1/4] drm: Introduce device wedged event
Date: Sat, 26 Oct 2024 14:15:15 +0800 [thread overview]
Message-ID: <202410261411.F8079SY8-lkp@intel.com> (raw)
In-Reply-To: <20241025084817.144621-2-raag.jadav@intel.com>
Hi Raag,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.12-rc4 next-20241025]
[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/Raag-Jadav/drm-Introduce-device-wedged-event/20241025-165119
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20241025084817.144621-2-raag.jadav%40intel.com
patch subject: [PATCH v8 1/4] drm: Introduce device wedged event
config: alpha-allmodconfig (https://download.01.org/0day-ci/archive/20241026/202410261411.F8079SY8-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241026/202410261411.F8079SY8-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/202410261411.F8079SY8-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/drm_drv.c:81:10: error: nonconstant array index in initializer
81 | [ffs(DRM_WEDGE_RECOVERY_REBIND) - 1] = "rebind",
| ^~~
drivers/gpu/drm/drm_drv.c:81:10: note: (near initialization for 'drm_wedge_recovery_opts')
drivers/gpu/drm/drm_drv.c:82:10: error: nonconstant array index in initializer
82 | [ffs(DRM_WEDGE_RECOVERY_BUS_RESET) - 1] = "bus-reset",
| ^~~
drivers/gpu/drm/drm_drv.c:82:10: note: (near initialization for 'drm_wedge_recovery_opts')
In file included from drivers/gpu/drm/drm_drv.c:30:
>> drivers/gpu/drm/drm_drv.c:84:51: error: expression in static assertion is not constant
84 | static_assert(ARRAY_SIZE(drm_wedge_recovery_opts) == ffs(DRM_WEDGE_RECOVERY_BUS_RESET));
include/linux/build_bug.h:78:56: note: in definition of macro '__static_assert'
78 | #define __static_assert(expr, msg, ...) _Static_assert(expr, msg)
| ^~~~
drivers/gpu/drm/drm_drv.c:84:1: note: in expansion of macro 'static_assert'
84 | static_assert(ARRAY_SIZE(drm_wedge_recovery_opts) == ffs(DRM_WEDGE_RECOVERY_BUS_RESET));
| ^~~~~~~~~~~~~
vim +81 drivers/gpu/drm/drm_drv.c
75
76 /*
77 * Available recovery methods for wedged device. To be sent along with device
78 * wedged uevent.
79 */
80 static const char *const drm_wedge_recovery_opts[] = {
> 81 [ffs(DRM_WEDGE_RECOVERY_REBIND) - 1] = "rebind",
82 [ffs(DRM_WEDGE_RECOVERY_BUS_RESET) - 1] = "bus-reset",
83 };
> 84 static_assert(ARRAY_SIZE(drm_wedge_recovery_opts) == ffs(DRM_WEDGE_RECOVERY_BUS_RESET));
85
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-10-26 6:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 8:48 [PATCH v8 0/4] Introduce DRM device wedged event Raag Jadav
2024-10-25 8:48 ` [PATCH v8 1/4] drm: Introduce " Raag Jadav
2024-10-25 9:08 ` Jani Nikula
2024-10-25 14:45 ` Andy Shevchenko
2024-10-26 15:27 ` Raag Jadav
2024-10-28 8:50 ` Jani Nikula
2024-10-26 6:15 ` kernel test robot [this message]
2024-10-26 10:10 ` kernel test robot
2024-10-25 8:48 ` [PATCH v8 2/4] drm/doc: Document " Raag Jadav
2024-10-29 9:51 ` Christian König
2024-11-01 4:26 ` Raag Jadav
2024-10-25 8:48 ` [PATCH v8 3/4] drm/xe: Use " Raag Jadav
2024-10-25 8:48 ` [PATCH v8 4/4] drm/i915: " Raag Jadav
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=202410261411.F8079SY8-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrealmeid@igalia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kernel-dev@igalia.com \
--cc=lina@asahilina.net \
--cc=lucas.demarchi@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=raag.jadav@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@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