From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <cl@linux.com>
Cc: Zimny Lech <napohybelskurwysynom2010@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for October 6
Date: Wed, 06 Oct 2010 22:23:47 +0300 [thread overview]
Message-ID: <4CACCCC3.5070203@cs.helsinki.fi> (raw)
In-Reply-To: <alpine.DEB.2.00.1010061319580.4817@router.home>
On 6.10.2010 21.20, Christoph Lameter wrote:
> On Wed, 6 Oct 2010, Pekka Enberg wrote:
>
>> You already acked my patch to fix it:
>>
>> http://lkml.org/lkml/2010/10/6/194
>
> That is a different issue.
It's the exact same build error and hotplug_memory_notifier() works just
fine on !CONFIG_MEMORY_HOTPLUG.
Pekka
next prev parent reply other threads:[~2010-10-06 19:23 UTC|newest]
Thread overview: 21+ 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 [this message]
2010-10-06 20:09 ` Christoph Lameter
2010-10-06 18:16 ` Zimny Lech
2010-10-06 18:14 ` Zimny Lech
2010-10-06 18:22 ` Zimny Lech
2010-10-26 8:08 ` Ingo Molnar
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: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
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=4CACCCC3.5070203@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=napohybelskurwysynom2010@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.