linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [zwisler:mmots_dax_tracepoint 14/143] mm/debug.c:34:21: error: expected expression before ',' token
Date: Fri, 6 Jan 2017 13:22:25 +0100	[thread overview]
Message-ID: <20170106122225.GK5556@dhcp22.suse.cz> (raw)
In-Reply-To: <201701062053.SDNkH5Uj%fengguang.wu@intel.com>

On Fri 06-01-17 20:13:06, Wu Fengguang wrote:
> 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,
>                         ^

I am pretty sure I have fixed this one but it got lost probably during
the rebase. Sorry about that. Here is the fixup which should be folded
into http://lkml.kernel.org/r/20170102153057.9451-3-mhocko@kernel.org

Thanks for reporting!
---

      reply	other threads:[~2017-01-06 12:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 12:13 [zwisler:mmots_dax_tracepoint 14/143] mm/debug.c:34:21: error: expected expression before ',' token kbuild test robot
2017-01-06 12:22 ` Michal Hocko [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=20170106122225.GK5556@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).