From: kernel test robot <lkp@intel.com>
To: Sami Tolvanen <samitolvanen@google.com>
Cc: kbuild-all@lists.01.org,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org, Alistair Delva <adelva@google.com>
Subject: [ammarfaizi2-block:google/android/kernel/common/android-gs-raviole-5.10-android12-qpr1-d 1249/8858] arch/mips/include/asm/page.h:12:10: fatal error: spaces.h: No such file or directory
Date: Mon, 21 Feb 2022 20:26:07 +0800 [thread overview]
Message-ID: <202202212057.fNaQFLep-lkp@intel.com> (raw)
Hi Sami,
FYI, the error/warning still remains.
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android-gs-raviole-5.10-android12-qpr1-d
head: 9771767708df4fcf51cd1642e041c804a86e740c
commit: 08f67ef189ecce0f8330e53e5b78157f1b5afa19 [1249/8858] ANDROID: module: cfi: ensure __cfi_check alignment
config: mips-allmodconfig (https://download.01.org/0day-ci/archive/20220221/202202212057.fNaQFLep-lkp@intel.com/config)
compiler: mips-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/08f67ef189ecce0f8330e53e5b78157f1b5afa19
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android-gs-raviole-5.10-android12-qpr1-d
git checkout 08f67ef189ecce0f8330e53e5b78157f1b5afa19
# 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=mips modules_prepare
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 >>):
In file included from scripts/module.lds.S:6:
>> arch/mips/include/asm/page.h:12:10: fatal error: spaces.h: No such file or directory
12 | #include <spaces.h>
| ^~~~~~~~~~
compilation terminated.
make[2]: *** [scripts/Makefile.build:367: scripts/module.lds] Error 1
make[1]: *** [Makefile:1469: modules_prepare] Error 2
make: *** [Makefile:185: __sub-make] Error 2
make: Target 'modules_prepare' not remade because of errors.
vim +12 arch/mips/include/asm/page.h
^1da177e4c3f41 include/asm-mips/page.h Linus Torvalds 2005-04-16 11
^1da177e4c3f41 include/asm-mips/page.h Linus Torvalds 2005-04-16 @12 #include <spaces.h>
99502d94c3649c arch/mips/include/asm/page.h Nelson Elhage 2009-07-31 13 #include <linux/const.h>
75b5b5e0a26279 arch/mips/include/asm/page.h Leonid Yegoshin 2013-11-14 14 #include <linux/kernel.h>
75b5b5e0a26279 arch/mips/include/asm/page.h Leonid Yegoshin 2013-11-14 15 #include <asm/mipsregs.h>
^1da177e4c3f41 include/asm-mips/page.h Linus Torvalds 2005-04-16 16
:::::: The code at line 12 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-21 12:26 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=202202212057.fNaQFLep-lkp@intel.com \
--to=lkp@intel.com \
--cc=adelva@google.com \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samitolvanen@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.