From: kbuild test robot <lkp@intel.com>
To: Waiman Long <longman@redhat.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Oscar Salvador <osalvador@suse.de>,
Tejun Heo <tj@kernel.org>, Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v2] include/linux/nodemask.h: Use nr_node_ids (not MAX_NUMNODES) in __nodemask_pr_numnodes()
Date: Wed, 19 Dec 2018 13:48:48 +0800 [thread overview]
Message-ID: <201812191307.AuoaLTFV%fengguang.wu@intel.com> (raw)
In-Reply-To: <1545169122-12579-1-git-send-email-longman@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]
Hi Waiman,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.20-rc7 next-20181218]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Waiman-Long/include-linux-nodemask-h-Use-nr_node_ids-not-MAX_NUMNODES-in-__nodemask_pr_numnodes/20181219-110121
config: arm-omap2plus_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=arm
All errors (new ones prefixed by >>):
kernel/cgroup/cpuset.o: In function `cpuset_common_seq_show':
>> cpuset.c:(.text+0xe2c): undefined reference to `nr_node_ids'
kernel/cgroup/cpuset.o: In function `cpuset_print_current_mems_allowed':
cpuset.c:(.text+0x4624): undefined reference to `nr_node_ids'
kernel/cgroup/cpuset.o: In function `cpuset_task_status_allowed':
cpuset.c:(.text+0x4d5c): undefined reference to `nr_node_ids'
mm/oom_kill.o: In function `dump_header':
oom_kill.c:(.text.unlikely+0x3c4): undefined reference to `nr_node_ids'
mm/page_alloc.o: In function `warn_alloc':
page_alloc.c:(.text+0x4ae0): undefined reference to `nr_node_ids'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34490 bytes --]
prev parent reply other threads:[~2018-12-19 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 21:38 Waiman Long
2018-12-18 23:20 ` Oscar Salvador
2018-12-19 5:48 ` kbuild test robot [this message]
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=201812191307.AuoaLTFV%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=osalvador@suse.de \
--cc=tj@kernel.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®