From: Zimny Lech <napohybelskurwysynom2010@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: linux-next: Tree for October 6
Date: Wed, 6 Oct 2010 20:16:11 +0200 [thread overview]
Message-ID: <AANLkTin8hb8JfDWkWXpnxkBZCD3nj-krpf7GSViarxqJ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010061311430.31538@router.home>
2010/10/6 Christoph Lameter <cl@linux.com>:
> On Wed, 6 Oct 2010, Zimny Lech wrote:
>
>> >> It seems that you forgot to push to repo
>> >> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=summary
>> >
>> > No, its just that the mirroring was slow/blocked :-(
>>
>> Ok, I pulled latest tree. Thanks.
>>
>> I already reported this before.
>>
>> /home/test/linux-2.6/mm/slub.c: In function 'kmem_cache_init':
>> /home/test/linux-2.6/mm/slub.c:3031:2: error: 'slab_memory_callback'
>> undeclared (first use in this function)
>> /home/test/linux-2.6/mm/slub.c:3031:2: note: each undeclared
>> identifier is reported only once for each function it appears in
>> make[2]: *** [mm/slub.o] Error 1
>> make[1]: *** [mm] Error 2
>> make: *** [sub-make] Error 2
>>
>> any thoughts?
>
>
> Subject: slub: hotplug_memory_notifier not useable for !CONFIG_MEMORY_HOTPLUG
>
> Add #ifdef to resolve the situation.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
Thanks for the quick reply :)
I'll check it later or in next -next
>
> ---
> mm/slub.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> Index: linux-2.6/mm/slub.c
> ===================================================================
> --- linux-2.6.orig/mm/slub.c 2010-10-06 13:10:00.000000000 -0500
> +++ linux-2.6/mm/slub.c 2010-10-06 13:10:25.000000000 -0500
> @@ -3028,7 +3028,9 @@ void __init kmem_cache_init(void)
> sizeof(struct kmem_cache_node),
> 0, SLAB_HWCACHE_ALIGN | SLAB_PANIC, NULL);
>
> +#ifdef CONFIG_MEMORY_HOTPLUG
> hotplug_memory_notifier(slab_memory_callback, SLAB_CALLBACK_PRI);
> +#endif
>
> /* Able to allocate the per node structures */
> slab_state = PARTIAL;
>
--
Slawa!
N.P.S.
Les fleurs du mal unfold
Comme les fleurs du mal
Dark demons of my soul
Un amour fatal
next prev parent reply other threads:[~2010-10-06 18:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 5:36 linux-next: Tree for October 6 Stephen Rothwell
2010-10-06 6:25 ` Zimny Lech
2010-10-06 6:48 ` Stephen Rothwell
2010-10-06 18:07 ` Zimny Lech
2010-10-06 18:12 ` Christoph Lameter
2010-10-06 18:15 ` Pekka Enberg
2010-10-06 18:20 ` Christoph Lameter
2010-10-06 19:23 ` Pekka Enberg
2010-10-06 20:09 ` Christoph Lameter
2010-10-06 18:16 ` Zimny Lech [this message]
2010-10-06 18:14 ` Zimny Lech
2010-10-06 18:22 ` Zimny Lech
2010-10-26 8:08 ` Ingo Molnar
[not found] ` <20101026080822.GA10520-X9Un+BFzKDI@public.gmane.org>
2010-10-26 12:32 ` Trond Myklebust
2010-10-26 12:41 ` Ingo Molnar
2010-10-26 12:57 ` Stephen Rothwell
[not found] ` <20101026124113.GA10872-X9Un+BFzKDI@public.gmane.org>
2010-10-26 17:52 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-10-06 5:52 Stephen Rothwell
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=AANLkTin8hb8JfDWkWXpnxkBZCD3nj-krpf7GSViarxqJ@mail.gmail.com \
--to=napohybelskurwysynom2010@gmail.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--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;
as well as URLs for NNTP newsgroup(s).