linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Christoph Lameter <cl@linux-foundation.org>,
	"Wu, Fengguang" <fengguang.wu@intel.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Chris Wright <chrisw@redhat.com>,
	"Huang, Ying" <ying.huang@intel.com>,
	Lin Ming <ming.m.lin@intel.com>,
	Josh Triplett <josh@joshtriplett.org>,
	Andi Kleen <andi@firstfloor.org>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	linux-mm@kvack.org
Subject: [RFC][PATCH 0/4] move tools in Documentation/vm/ to tools/vm/
Date: Wed, 02 Sep 2009 11:41:25 +0800	[thread overview]
Message-ID: <20090902034125.718886329@intel.com> (raw)

Hi all,

3 useful tools (which are more than code examples) in Documentation/vm/
	- page-types
	- slabinfo
	- slqbinfo
are moved to tools/vm/, and page-types is updated to support two new flags.

The tools can be compiled together by

	make tools/vm/

Note that checkpatch complains some style problems on slabinfo.c/slqbinfo.c,
which are leaved as is.

Thanks,
Fengguang
-- 

--
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>

             reply	other threads:[~2009-09-02  4:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02  3:41 Wu Fengguang [this message]
2009-09-02  3:41 ` [RFC][PATCH 1/4] page-types: move from Documentation/vm/ to tools/vm/ Wu Fengguang
2009-09-02  3:41 ` [RFC][PATCH 2/4] slabinfo: " Wu Fengguang
2009-09-02  4:17   ` [RFC][PATCH 2/4 v2] " Wu Fengguang
2009-09-02 18:04     ` Christoph Lameter
2009-09-02  3:41 ` [RFC][PATCH 3/4] pagemap: export KPF_HWPOISON Wu Fengguang
2009-09-02  3:41 ` [RFC][PATCH 4/4] pagemap: document KPF_KSM and show it in page-types Wu Fengguang

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=20090902034125.718886329@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=chrisw@redhat.com \
    --cc=cl@linux-foundation.org \
    --cc=josh@joshtriplett.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ming.m.lin@intel.com \
    --cc=nickpiggin@yahoo.com.au \
    --cc=randy.dunlap@oracle.com \
    --cc=ying.huang@intel.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).