From: kernel test robot <lkp@intel.com>
To: Xiang Liu <xiang.liu@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Alex Deucher <alexander.deucher@amd.com>,
YiPeng Chai <YiPeng.Chai@amd.com>,
Hawking Zhang <Hawking.Zhang@amd.com>
Subject: [agd5f:amd-staging-drm-next 1/107] drivers/gpu/drm/amd/amdgpu/../ras/ras_mgr/amdgpu_ras_mce.c:28:10: fatal error: 'asm/mce.h' file not found
Date: Fri, 21 Aug 2026 00:09:39 +0800 [thread overview]
Message-ID: <202608202308.OWeUNNWV-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/agd5f/linux.git amd-staging-drm-next
head: 232bf7d5453df6cc0d877a1003f9aa172e9750de
commit: 3a980c04ebdfd427c67cfac6315e24b11f1b1126 [1/107] drm/amd/ras: register mce notifier to obtain ras error info
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20260820/202608202308.OWeUNNWV-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 935bfc708590c60147a79c7df145bb6e68b1d388)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260820/202608202308.OWeUNNWV-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/202608202308.OWeUNNWV-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../ras/ras_mgr/amdgpu_ras_mce.c:28:10: fatal error: 'asm/mce.h' file not found
28 | #include <asm/mce.h>
| ^~~~~~~~~~~
1 error generated.
vim +28 drivers/gpu/drm/amd/amdgpu/../ras/ras_mgr/amdgpu_ras_mce.c
> 28 #include <asm/mce.h>
29
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-20 16:09 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=202608202308.OWeUNNWV-lkp@intel.com \
--to=lkp@intel.com \
--cc=Hawking.Zhang@amd.com \
--cc=YiPeng.Chai@amd.com \
--cc=alexander.deucher@amd.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=xiang.liu@amd.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