From: Christoph Lameter <cl@linux.com>
To: Dave Young <dyoung@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, xiyou.wangcong@gmail.com,
penberg@kernel.org, fengguang.wu@intel.com
Subject: Re: [PATCH 2/3] move slabinfo.c to tools/vm
Date: Mon, 6 Feb 2012 08:51:48 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.00.1202060851260.393@router.home> (raw)
In-Reply-To: <20120205081550.GA2247@darkstar.redhat.com>
On Sun, 5 Feb 2012, Dave Young wrote:
> We have tools/vm/ folder for vm tools, so move slabinfo.c
> from tools/slub/ to tools/vm/
Acked-by: Christoph Lameter <cl@linux.com>
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-02-06 14:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 8:15 Dave Young
2012-02-06 14:51 ` Christoph Lameter [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=alpine.DEB.2.00.1202060851260.393@router.home \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=xiyou.wangcong@gmail.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