linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Vladimir Davydov <vdavydov@parallels.com>,
	kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [mmotm:master 143/283] mm/slab.c:3260:4: error: implicit declaration of function 'slab_free'
Date: Thu, 6 Nov 2014 10:08:45 +0100	[thread overview]
Message-ID: <20141106090845.GA17744@dhcp22.suse.cz> (raw)
In-Reply-To: <201411060959.OFpcU713%fengguang.wu@intel.com>

Hi,
I have encountered the same error as well. We need to move the forward
declaration up outside of CONFIG_NUMA:
---

  reply	other threads:[~2014-11-06  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06  1:16 kbuild test robot
2014-11-06  9:08 ` Michal Hocko [this message]
2014-11-06  9:28   ` Vladimir Davydov
2014-11-06 14:05     ` Michal Hocko
2014-11-06 14:30       ` Vladimir Davydov
2014-11-06 14:33         ` Michal Hocko
2014-11-06  9:13 ` Vladimir Davydov

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=20141106090845.GA17744@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.org \
    --cc=vdavydov@parallels.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