From: kernel test robot <lkp@intel.com>
To: Borislav Petkov <bp@suse.de>
Cc: kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org
Subject: [ammarfaizi2-block:bp/bp/test 21/23] drivers/edac/ghes_edac.c:18:10: fatal error: asm/mce.h: No such file or directory
Date: Mon, 4 Apr 2022 09:09:53 +0800 [thread overview]
Message-ID: <202204040936.kxNxgvNn-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block bp/bp/test
head: aff0e90f2a981e0350187c8a931071d7f35df6e5
commit: ef3a8acde71eb676a92d9f3158d7f112061e2bf9 [21/23] ghes_edac: Convert MCE to its representation
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20220404/202204040936.kxNxgvNn-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/ammarfaizi2/linux-block/commit/ef3a8acde71eb676a92d9f3158d7f112061e2bf9
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block bp/bp/test
git checkout ef3a8acde71eb676a92d9f3158d7f112061e2bf9
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/edac/ghes_edac.c:18:10: fatal error: asm/mce.h: No such file or directory
18 | #include <asm/mce.h>
| ^~~~~~~~~~~
compilation terminated.
vim +18 drivers/edac/ghes_edac.c
17
> 18 #include <asm/mce.h>
19
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-04 1:10 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=202204040936.kxNxgvNn-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@suse.de \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®