From: kernel test robot <lkp@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: [mingo-tip:sched/headers 12/2340] include/linux/entry-common.h:11:10: fatal error: asm/entry-common.h: No such file or directory
Date: Thu, 24 Feb 2022 08:45:58 +0800 [thread overview]
Message-ID: <202202240812.Ynrlsu5B-lkp@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git sched/headers
head: 97c5eeb4de3ad324ed2a4656b46465299cfd010a
commit: e66f6481a8c748ce2d4b37a3d5e10c4dd0d65e80 [12/2340] sched/headers: Reorganize, clean up and optimize kernel/sched/core.c dependencies
config: arm64-randconfig-r033-20220223 (https://download.01.org/0day-ci/archive/20220224/202202240812.Ynrlsu5B-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://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git/commit/?id=e66f6481a8c748ce2d4b37a3d5e10c4dd0d65e80
git remote add mingo-tip git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git
git fetch --no-tags mingo-tip sched/headers
git checkout e66f6481a8c748ce2d4b37a3d5e10c4dd0d65e80
# 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>
Note: the mingo-tip/sched/headers HEAD 97c5eeb4de3ad324ed2a4656b46465299cfd010a builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
In file included from kernel/sched/core.c:66:
>> include/linux/entry-common.h:11:10: fatal error: asm/entry-common.h: No such file or directory
11 | #include <asm/entry-common.h>
| ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +11 include/linux/entry-common.h
142781e108b13b Thomas Gleixner 2020-07-22 10
142781e108b13b Thomas Gleixner 2020-07-22 @11 #include <asm/entry-common.h>
142781e108b13b Thomas Gleixner 2020-07-22 12
:::::: The code at line 11 was first introduced by commit
:::::: 142781e108b13b2b0e8f035cfb5bfbbc8f14d887 entry: Provide generic syscall entry functionality
:::::: TO: Thomas Gleixner <tglx@linutronix.de>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-24 2:24 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=202202240812.Ynrlsu5B-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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®