From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <cl@linux.com>
Cc: linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [S+Q Cleanup4 0/6] SLUB: Cleanups V4
Date: Mon, 23 Aug 2010 20:17:01 +0300 [thread overview]
Message-ID: <4C72AD0D.7040100@cs.helsinki.fi> (raw)
In-Reply-To: <20100820173711.136529149@linux.com>
On 20.8.2010 20.37, Christoph Lameter wrote:
> I think it may be best to first try to merge these and make sure that
> they are fine before we go step by step through the unification patches.
> I hope they can go into -next.
I've applied these patches and queued them for -next. Thanks guys!
--
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>
prev parent reply other threads:[~2010-08-23 17:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 17:37 [S+Q Cleanup4 0/6] SLUB: Cleanups V4 Christoph Lameter
2010-08-20 17:37 ` [S+Q Cleanup4 1/6] Slub: Force no inlining of debug functions Christoph Lameter
2010-08-20 17:37 ` [S+Q Cleanup4 2/6] slub: remove dynamic dma slab allocation Christoph Lameter
2010-08-20 17:37 ` [S+Q Cleanup4 3/6] slub: Remove static kmem_cache_cpu array for boot Christoph Lameter
2010-08-20 17:37 ` [S+Q Cleanup4 4/6] slub: Dynamically size kmalloc cache allocations Christoph Lameter
2010-08-20 17:37 ` [S+Q Cleanup4 5/6] slub: Extract hooks for memory checkers from hotpaths Christoph Lameter
2010-08-20 17:37 ` [S+Q Cleanup4 6/6] slub: Move gfpflag masking out of the hotpath Christoph Lameter
2010-08-20 21:06 ` [S+Q Cleanup4 0/6] SLUB: Cleanups V4 David Rientjes
2010-08-20 23:12 ` Christoph Lameter
2010-08-20 23:53 ` David Rientjes
2010-08-23 17:17 ` Pekka Enberg [this message]
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=4C72AD0D.7040100@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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).