From: kernel test robot <lkp@intel.com>
To: Michal Hocko <mhocko@suse.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Oscar Salvador <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [hnaz-mm:master 209/343] page_alloc.c:undefined reference to `node_data'
Date: Thu, 24 Feb 2022 09:58:16 +0800 [thread overview]
Message-ID: <202202240938.3y49V1yT-lkp@intel.com> (raw)
tree: https://github.com/hnaz/linux-mm master
head: 8857950589bc3b4920d69c3e0b2c06d33f445d21
commit: 76fea45fe1651bb00c2b6ec34341fb3e130dd1b0 [209/343] mm: handle uninitialized numa nodes gracefully
config: mips-randconfig-c004-20220223 (https://download.01.org/0day-ci/archive/20220224/202202240938.3y49V1yT-lkp@intel.com/config)
compiler: mips64el-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/hnaz/linux-mm/commit/76fea45fe1651bb00c2b6ec34341fb3e130dd1b0
git remote add hnaz-mm https://github.com/hnaz/linux-mm
git fetch --no-tags hnaz-mm master
git checkout 76fea45fe1651bb00c2b6ec34341fb3e130dd1b0
# 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 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 >>):
mips64el-linux-ld: mm/page_alloc.o: in function `free_area_init':
>> page_alloc.c:(.init.text+0x1f3c): undefined reference to `node_data'
>> mips64el-linux-ld: page_alloc.c:(.init.text+0x1f54): undefined reference to `node_data'
---
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 1:59 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=202202240938.3y49V1yT-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
/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