From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: kbuild test robot <lkp@intel.com>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH V2 2/2] mm: Add sysfs interface to dump each node's zonelist information
Date: Tue, 06 Sep 2016 12:19:05 +0530 [thread overview]
Message-ID: <57CE66E1.1070105@linux.vnet.ibm.com> (raw)
In-Reply-To: <201609061410.GxOTG4KX%fengguang.wu@intel.com>
On 09/06/2016 11:41 AM, kbuild test robot wrote:
> Hi Anshuman,
>
> [auto build test ERROR on mmotm/master]
> [also build test ERROR on v4.8-rc5 next-20160905]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
> [Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
> [Check https://git-scm.com/docs/git-format-patch for more information]
>
> url: https://github.com/0day-ci/linux/commits/Anshuman-Khandual/mm-Export-definition-of-zone_names-array-through-mmzone-h/20160906-133749
> base: git://git.cmpxchg.org/linux-mmotm.git master
> config: x86_64-randconfig-x013-201636 (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> drivers/base/memory.c: In function 'dump_zonelists':
>>> >> drivers/base/memory.c:474:20: error: 'ZONELIST_NOFALLBACK' undeclared (first use in this function)
> node_zonelists[ZONELIST_NOFALLBACK]);
> ^~~~~~~~~~~~~~~~~~~
> drivers/base/memory.c:474:20: note: each undeclared identifier is reported only once for each function it appears in
>
> vim +/ZONELIST_NOFALLBACK +474 drivers/base/memory.c
>
> 468 node_zonelists[ZONELIST_FALLBACK]);
> 469 count += sprintf(buf + count, "[NODE (%d)]\n", node);
> 470 count += sprintf(buf + count, "\tZONELIST_FALLBACK\n");
> 471 count += dump_zonelist(buf + count, zonelist);
> 472
> 473 zonelist = &(NODE_DATA(node)->
> > 474 node_zonelists[ZONELIST_NOFALLBACK]);
> 475 count += sprintf(buf + count, "\tZONELIST_NOFALLBACK\n");
Missed the fact that ZONELIST_NOFALLBACK is valid only on CONFIG_NUMA
systems. Will fix and resend the patch.
next prev parent reply other threads:[~2016-09-06 6:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 5:34 [PATCH V2 1/2] mm: Export definition of 'zone_names' array through mmzone.h Anshuman Khandual
2016-09-06 5:34 ` [PATCH V2 2/2] mm: Add sysfs interface to dump each node's zonelist information Anshuman Khandual
2016-09-06 6:11 ` kbuild test robot
2016-09-06 6:49 ` Anshuman Khandual [this message]
2016-09-06 8:31 ` [PATCH V3] " Anshuman Khandual
2016-09-06 9:05 ` kbuild test robot
2016-09-07 12:32 ` Anshuman Khandual
2016-09-06 20:36 ` Dave Hansen
2016-09-07 3:08 ` Kees Cook
2016-09-07 4:00 ` Anshuman Khandual
2016-09-08 2:46 ` [PATCH V4] " Anshuman Khandual
2016-09-08 7:44 ` kbuild test robot
2016-09-08 20:24 ` Dave Hansen
2016-09-12 5:27 ` Anshuman Khandual
2016-09-12 18:13 ` David Rientjes
2016-09-17 4:26 ` Anshuman Khandual
2016-09-20 0:54 ` David Rientjes
2016-10-13 14:38 ` Anshuman Khandual
2016-09-09 13:36 ` Michal Hocko
2016-09-12 5:24 ` Anshuman Khandual
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=57CE66E1.1070105@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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).