From: Randy Dunlap <randy.dunlap@oracle.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org
Subject: Re: slub: move slabinfo.c to tools/slub/slabinfo.c
Date: Thu, 21 Oct 2010 11:16:26 -0700 [thread overview]
Message-ID: <20101021111626.e3f214f5.randy.dunlap@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010211300550.24115@router.home>
On Thu, 21 Oct 2010 13:01:56 -0500 (CDT) Christoph Lameter wrote:
> We now have a tools directory for these things.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
Any special build/make rules needed, or just use straight 'gcc slabinfo.c -o slabinfo' ?
(as listed in the source file :)
Why move only this one source file from Documentation/vm/ ?
There are several others there.
> ---
> Documentation/vm/slabinfo.c | 1364 --------------------------------------------
> tools/slub/slabinfo.c | 1364 ++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 1364 insertions(+), 1364 deletions(-)
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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-10-21 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 18:01 slub: move slabinfo.c to tools/slub/slabinfo.c Christoph Lameter
2010-10-21 18:16 ` Randy Dunlap [this message]
2010-10-21 18:24 ` Christoph Lameter
2010-10-22 1:39 ` KOSAKI Motohiro
2010-10-26 17:14 ` Pekka Enberg
2010-10-21 20:15 ` David Rientjes
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=20101021111626.e3f214f5.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=cl@linux.com \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
--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).