From: kernel test robot <lkp@intel.com>
To: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, intel-xe@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Raag Jadav <raag.jadav@intel.com>
Subject: [drm-xe:drm-xe-next 8/9] drivers/gpu/drm/xe/xe_debugfs.c:46:1: sparse: sparse: symbol 'wedge_cold_reset' was not declared. Should it be static?
Date: Sat, 15 Aug 2026 20:17:54 +0800 [thread overview]
Message-ID: <202608151936.YwZijiM8-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
head: 9736ca77f060472d196c118c5f14943b4606f6d3
commit: f29c2bd7eaeb73afcdbd4e3bbf54d6f8799a9b06 [8/9] drm/xe/ras: Use fault-inject to trigger cold-reset wedge
config: i386-randconfig-061-20260815 (https://download.01.org/0day-ci/archive/20260815/202608151936.YwZijiM8-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260815/202608151936.YwZijiM8-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/202608151936.YwZijiM8-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/xe/xe_debugfs.c:46:1: sparse: sparse: symbol 'wedge_cold_reset' was not declared. Should it be static?
vim +/wedge_cold_reset +46 drivers/gpu/drm/xe/xe_debugfs.c
43
> 44 DECLARE_FAULT_ATTR(gt_reset_failure);
45 DECLARE_FAULT_ATTR(inject_csc_hw_error);
> 46 DECLARE_FAULT_ATTR(wedge_cold_reset);
47
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-15 12:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202608151936.YwZijiM8-lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mallesh.koujalagi@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=raag.jadav@intel.com \
--cc=rodrigo.vivi@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