From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Haicheng Li <haicheng.li@linux.intel.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
linux-mm@kvack.org, Matt Mackall <mpm@selenic.com>,
Andi Kleen <andi@firstfloor.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] slab: initialize unused alien cache entry as NULL at alloc_alien_cache().
Date: Wed, 6 Jan 2010 10:20:42 +0200 [thread overview]
Message-ID: <84144f021001060020v57535d5bwc65b482eca669bc5@mail.gmail.com> (raw)
In-Reply-To: <4B443AE3.2080800@linux.intel.com>
On Wed, Jan 6, 2010 at 9:25 AM, Haicheng Li <haicheng.li@linux.intel.com> wrote:
> Comparing with existing code, it's a simpler way to use kzalloc_node()
> to ensure that each unused alien cache entry is NULL.
>
> CC: Pekka Enberg <penberg@cs.helsinki.fi>
> CC: Eric Dumazet <eric.dumazet@gmail.com>
> Acked-by: Andi Kleen <ak@linux.intel.com>
> Acked-by: Christoph Lameter <cl@linux-foundation.org>
> Reviewed-by: Matt Mackall <mpm@selenic.com>
> Signed-off-by: Haicheng Li <haicheng.li@linux.intel.com>
I can find a trace of Andi acking the previous version of this patch
but I don't see an ACK from Christoph nor a revieved-by from Matt. Was
I not CC'd on those emails or what's going on here?
Pekka
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-01-06 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 7:25 [PATCH v3] slab: initialize unused alien cache entry as NULL at alloc_alien_cache() Haicheng Li
2010-01-06 8:20 ` Pekka Enberg [this message]
2010-01-06 8:39 ` Haicheng Li
2010-01-06 8:42 ` Pekka Enberg
2010-01-06 8:46 ` Haicheng Li
2010-01-07 17:57 ` Christoph Lameter
2010-01-07 12:11 ` Pekka Enberg
2010-01-07 18:10 ` Matt Mackall
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=84144f021001060020v57535d5bwc65b482eca669bc5@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--cc=haicheng.li@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.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;
as well as URLs for NNTP newsgroup(s).