From: Caspar Zhang <caspar@casparzhang.com>
To: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH 2/2] mm/ksm,oom: fix count_numa()
Date: Mon, 20 Feb 2012 19:37:28 +0800 [thread overview]
Message-ID: <4F423078.3030104@casparzhang.com> (raw)
In-Reply-To: <1329735301-17676-2-git-send-email-caspar@casparzhang.com>
On 02/20/2012 06:55 PM, Caspar Zhang wrote:
> This patch makes ksm on oom tests use the new count_numa() function.
oops, should be s/on/and. I've changed it in my local commit.
Caspar
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-02-20 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 10:55 [LTP] [PATCH 1/2] mm/lib: change count_numa() behavior Caspar Zhang
2012-02-20 10:55 ` [LTP] [PATCH 2/2] mm/ksm,oom: fix count_numa() Caspar Zhang
2012-02-20 11:37 ` Caspar Zhang [this message]
2012-02-20 13:52 ` Zhouping Liu
2012-02-20 12:21 ` [LTP] [PATCH 3/2] mm: fix possible node missing in write_cpusets Caspar Zhang
2012-02-20 12:38 ` [LTP] [PATCH 1/2] mm/lib: change count_numa() behavior Markos Chandras
2012-02-20 13:30 ` Zhouping Liu
2012-02-21 3:05 ` [LTP] [PATCH 3/2 v2] mm: fix possible node missing in write_cpusets Caspar Zhang
2012-02-21 3:06 ` [LTP] [PATCH 4/2] mem/lib: replace buf with path in correct place Caspar Zhang
2012-02-21 5:28 ` [LTP] [PATCH 1/2] mm/lib: change count_numa() behavior Caspar Zhang
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=4F423078.3030104@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=ltp-list@lists.sourceforge.net \
/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