From: kernel test robot <lkp@intel.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Greentime Hu <greentime.hu@sifive.com>,
Anup Patel <anup@brainfault.org>
Subject: [linux-next:master 3118/12657] page_alloc.c:undefined reference to `node_reclaim_distance'
Date: Fri, 26 Feb 2021 20:30:34 +0800 [thread overview]
Message-ID: <202102262031.5XSbXtfV-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: d01f2f7e35573049673b71e18be7abfe3f80323f
commit: 4f0e8eef772ee4438f304b2178bc28c958b6c13d [3118/12657] riscv: Add numa support for riscv64 platform
config: riscv-randconfig-p001-20210226 (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4f0e8eef772ee4438f304b2178bc28c958b6c13d
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 4f0e8eef772ee4438f304b2178bc28c958b6c13d
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
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 >>):
riscv32-linux-ld: mm/page_alloc.o: in function `get_page_from_freelist':
>> page_alloc.c:(.text+0xe028): undefined reference to `node_reclaim_distance'
>> riscv32-linux-ld: page_alloc.c:(.text+0xe02c): undefined reference to `node_reclaim_distance'
---
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: 25662 bytes --]
reply other threads:[~2021-02-26 12:30 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=202102262031.5XSbXtfV-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=greentime.hu@sifive.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=palmerdabbelt@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 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).