From: Pekka Enberg <penberg@iki.fi>
To: Christoph Lameter <cl@linux.com>, Jim Davis <jim.epost@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
penberg@kernel.org, mpm@selenic.com, linux-mm@kvack.org
Subject: Re: randconfig build error with next-20140512, in mm/slub.c
Date: Mon, 12 May 2014 21:53:58 +0300 [thread overview]
Message-ID: <537118C6.7050203@iki.fi> (raw)
In-Reply-To: <alpine.DEB.2.10.1405121346370.30318@gentwo.org>
On 05/12/2014 09:47 PM, Christoph Lameter wrote:
> A patch was posted today for this issue.
AFAICT, it's coming from -mm. Andrew, can you pick up the fix?
> Date: Mon, 12 May 2014 09:36:30 -0300
> From: Fabio Estevam <fabio.estevam@freescale.com>
> To: akpm@linux-foundation.org
> Cc: linux-mm@kvack.org, festevam@gmail.com, Fabio Estevam
> <fabio.estevam@freescale.com>, Christoph Lameter <cl@linux.com>, David Rientjes <rientjes@google.com>, Pekka Enberg <penberg@kernel.org>
> Subject: [PATCH] mm: slub: Place count_partial() outside CONFIG_SLUB_DEBUG if block
>
>
> On Mon, 12 May 2014, Jim Davis wrote:
>
>> Building with the attached random configuration file,
>>
>> mm/slub.c: In function ‘show_slab_objects’:
>> mm/slub.c:4361:5: error: implicit declaration of function ‘count_partial’ [-Werr
>> or=implicit-function-declaration]
>> x = count_partial(n, count_total);
>> ^
>> cc1: some warnings being treated as errors
>> make[1]: *** [mm/slub.o] Error 1
> >
next prev parent reply other threads:[~2014-05-12 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 18:08 Jim Davis
2014-05-12 18:47 ` Christoph Lameter
2014-05-12 18:53 ` Pekka Enberg [this message]
2014-05-12 20:36 ` David Rientjes
2014-05-13 0:31 ` Stephen Rothwell
2014-05-12 21:51 ` Fabio Estevam
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=537118C6.7050203@iki.fi \
--to=penberg@iki.fi \
--cc=cl@linux.com \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=sfr@canb.auug.org.au \
/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