From: kernel test robot <lkp@intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [norov:demotion 5/6] mempolicy.c:undefined reference to `set_demotion_target'
Date: Sun, 8 Aug 2021 20:57:19 +0800 [thread overview]
Message-ID: <202108082016.XQxcKKCZ-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
tree: https://github.com/norov/linux demotion
head: 78c3964952da24c07f2e34dc2d485fd2e6d5ba82
commit: 101e14d51cae3a28013f4e073b7067e405df0521 [5/6] sysfs: add /sys/kernel/mm/numa/demotion_list
config: riscv-allyesconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 10.3.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/norov/linux/commit/101e14d51cae3a28013f4e073b7067e405df0521
git remote add norov https://github.com/norov/linux
git fetch --no-tags norov demotion
git checkout 101e14d51cae3a28013f4e073b7067e405df0521
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross O=build_dir ARCH=riscv 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 >>):
riscv64-linux-ld: mm/mempolicy.o: in function `.L271':
>> mempolicy.c:(.text+0x233e): undefined reference to `set_demotion_target'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 70623 bytes --]
next reply other threads:[~2021-08-08 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 12:57 kernel test robot [this message]
2021-08-11 22:22 [norov:demotion 5/6] mempolicy.c:undefined reference to `set_demotion_target' kernel test robot
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=202108082016.XQxcKKCZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yury.norov@gmail.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;
as well as URLs for NNTP newsgroup(s).