From: Dave Young <dyoung@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dave Young <hidave.darkstar@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] move vm tools from Documentation/vm/ to tools/
Date: Fri, 03 Feb 2012 09:31:41 +0800 [thread overview]
Message-ID: <4F2B38FD.50902@redhat.com> (raw)
In-Reply-To: <20120202115628.46150903.akpm@linux-foundation.org>
On 02/03/2012 03:56 AM, Andrew Morton wrote:
> On Thu, 2 Feb 2012 10:13:43 +0800
> Dave Young <hidave.darkstar@gmail.com> wrote:
>
>> On Thu, Feb 2, 2012 at 5:17 AM, Andrew Morton <akpm@linux-foundation.org> wrote:
>>> On Wed, 1 Feb 2012 14:34:20 +0800
>>> Dave Young <dyoung@redhat.com> wrote:
>>>
>>>> tools/ is the better place for vm tools which are used by many people.
>>>> Moving them to tools also make them open to more users instead of hide in
>>>> Documentation folder.
>>>>
>>>
>>> It would be nice to covert these into simple pass/fail tests and
>>> promote them to tools/testing/selftests/.
>>
>> Andrew, I'm not clear about this, do you means to selftest
>> hugepage-mmap.c, hugepage-shm.c and map_hugetlb.c?
>
> Those ones can go into selftests.
>
>> I think slabinfo and page-types should stay in tools/vm/.
>
> Yes, those are tools, not selftests.
Great, thanks for explain, will do
--
Thanks
Dave
prev parent reply other threads:[~2012-02-03 1:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 6:34 [PATCH] move vm tools from Documentation/vm/ to tools/ Dave Young
2012-02-01 6:45 ` Cong Wang
2012-02-01 7:39 ` Dave Young
2012-02-01 7:32 ` Pekka Enberg
2012-02-01 7:41 ` Dave Young
2012-02-01 8:30 ` Wu Fengguang
2012-02-01 8:44 ` Pekka Enberg
2012-02-01 9:53 ` Dave Young
2012-02-01 9:53 ` Dave Young
2012-02-01 14:40 ` Christoph Lameter
2012-02-01 21:17 ` Andrew Morton
2012-02-02 2:13 ` Dave Young
2012-02-02 7:32 ` Cong Wang
2012-02-02 19:58 ` Andrew Morton
2012-02-02 19:56 ` Andrew Morton
2012-02-03 1:31 ` Dave Young [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=4F2B38FD.50902@redhat.com \
--to=dyoung@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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).