From: kbuild test robot <fengguang.wu@intel.com>
To: Michal Hocko <mhocko@suse.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [zwisler:mmots_dax_tracepoint 14/143] mm/debug.c:34:21: error: expected expression before ',' token
Date: Fri, 6 Jan 2017 20:13:06 +0800 [thread overview]
Message-ID: <201701062053.SDNkH5Uj%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2563 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/zwisler/linux.git mmots_dax_tracepoint
head: da4c62b5ae469ab971d717cd9a6f7651aabe5ab9
commit: ed24c07ce938fb44d97d5db5d653b5d51c608ec4 [14/143] mm: get rid of __GFP_OTHER_NODE
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout ed24c07ce938fb44d97d5db5d653b5d51c608ec4
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> mm/debug.c:34:21: error: expected expression before ',' token
__def_gfpflag_names,
^
vim +34 mm/debug.c
7cd12b4ab Vlastimil Babka 2016-03-15 18 char *migrate_reason_names[MR_TYPES] = {
7cd12b4ab Vlastimil Babka 2016-03-15 19 "compaction",
7cd12b4ab Vlastimil Babka 2016-03-15 20 "memory_failure",
7cd12b4ab Vlastimil Babka 2016-03-15 21 "memory_hotplug",
7cd12b4ab Vlastimil Babka 2016-03-15 22 "syscall_or_cpuset",
7cd12b4ab Vlastimil Babka 2016-03-15 23 "mempolicy_mbind",
7cd12b4ab Vlastimil Babka 2016-03-15 24 "numa_misplaced",
7cd12b4ab Vlastimil Babka 2016-03-15 25 "cma",
7cd12b4ab Vlastimil Babka 2016-03-15 26 };
7cd12b4ab Vlastimil Babka 2016-03-15 27
edf14cdbf Vlastimil Babka 2016-03-15 28 const struct trace_print_flags pageflag_names[] = {
edf14cdbf Vlastimil Babka 2016-03-15 29 __def_pageflag_names,
edf14cdbf Vlastimil Babka 2016-03-15 30 {0, NULL}
edf14cdbf Vlastimil Babka 2016-03-15 31 };
edf14cdbf Vlastimil Babka 2016-03-15 32
edf14cdbf Vlastimil Babka 2016-03-15 33 const struct trace_print_flags gfpflag_names[] = {
edf14cdbf Vlastimil Babka 2016-03-15 @34 __def_gfpflag_names,
edf14cdbf Vlastimil Babka 2016-03-15 35 {0, NULL}
420adbe9f Vlastimil Babka 2016-03-15 36 };
420adbe9f Vlastimil Babka 2016-03-15 37
edf14cdbf Vlastimil Babka 2016-03-15 38 const struct trace_print_flags vmaflag_names[] = {
edf14cdbf Vlastimil Babka 2016-03-15 39 __def_vmaflag_names,
edf14cdbf Vlastimil Babka 2016-03-15 40 {0, NULL}
82742a3a5 Sasha Levin 2014-10-09 41 };
82742a3a5 Sasha Levin 2014-10-09 42
:::::: The code at line 34 was first introduced by commit
:::::: edf14cdbf9a0e5ab52698ca66d07a76ade0d5c46 mm, printk: introduce new format string for flags
:::::: TO: Vlastimil Babka <vbabka@suse.cz>
:::::: CC: Linus Torvalds <torvalds@linux-foundation.org>
---
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: 6397 bytes --]
next reply other threads:[~2017-01-06 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 12:13 kbuild test robot [this message]
2017-01-06 12:22 ` [zwisler:mmots_dax_tracepoint 14/143] mm/debug.c:34:21: error: expected expression before ',' token Michal Hocko
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=201701062053.SDNkH5Uj%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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).