From: kbuild test robot <lkp@intel.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: kbuild-all@01.org, linux-mm@kvack.org, akpm@linux-foundation.org,
mhocko@suse.com, osalvador@suse.de, david@redhat.com
Subject: Re: [PATCH] mm, memory_hotplug: pass next_memory_node to new_page_nodemask()
Date: Fri, 14 Dec 2018 04:10:02 +0800 [thread overview]
Message-ID: <201812140424.sMFxJiyk%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181213032744.68323-1-richard.weiyang@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
Hi Wei,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.20-rc6 next-20181213]
[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/Wei-Yang/mm-memory_hotplug-pass-next_memory_node-to-new_page_nodemask/20181214-030950
config: x86_64-randconfig-x009-201849 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
mm/memory_hotplug.c: In function 'new_node_page':
>> mm/memory_hotplug.c:1339:33: error: implicit declaration of function 'next_memory_node'; did you mean 'first_memory_node'? [-Werror=implicit-function-declaration]
return new_page_nodemask(page, next_memory_node(nid), &nmask);
^~~~~~~~~~~~~~~~
first_memory_node
cc1: some warnings being treated as errors
vim +1339 mm/memory_hotplug.c
1324
1325 static struct page *new_node_page(struct page *page, unsigned long private)
1326 {
1327 int nid = page_to_nid(page);
1328 nodemask_t nmask = node_states[N_MEMORY];
1329
1330 /*
1331 * try to allocate from a different node but reuse this node if there
1332 * are no other online nodes to be used (e.g. we are offlining a part
1333 * of the only existing node)
1334 */
1335 node_clear(nid, nmask);
1336 if (nodes_empty(nmask))
1337 node_set(nid, nmask);
1338
> 1339 return new_page_nodemask(page, next_memory_node(nid), &nmask);
1340 }
1341
---
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: 26734 bytes --]
prev parent reply other threads:[~2018-12-13 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 3:27 Wei Yang
2018-12-13 4:03 ` Wei Yang
2018-12-13 20:10 ` 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=201812140424.sMFxJiyk%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=richard.weiyang@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