From: "Jörn Engel" <joern@logfs.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/2] hugetlb fixes
Date: Tue, 18 Jun 2013 16:04:33 -0400 [thread overview]
Message-ID: <20130618200433.GA28198@logfs.org> (raw)
In-Reply-To: <20130618132705.c5eb78a20499beb1b769f741@linux-foundation.org>
On Tue, 18 June 2013 13:27:05 -0700, Andrew Morton wrote:
> On Tue, 18 Jun 2013 14:50:55 -0400 J__rn Engel <joern@logfs.org> wrote:
>
> > On Tue, 18 June 2013 14:47:03 -0400, Joern Engel wrote:
> > >
> > > Test program below is failing before these two patches and passing
> > > after.
> >
> > Actually, do we have a place to stuff kernel tests? And if not,
> > should we have one?
>
> Yep, tools/testing/selftests/vm. It's pretty simple and stupid at
> present - it anything about the framework irritates you, please fix it!
Just did. :)
Jörn
--
Maintenance in other professions and of other articles is concerned with
the return of the item to its original state; in Software, maintenance
is concerned with moving an item away from its original state.
-- Les Belady
prev parent reply other threads:[~2013-06-18 21:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 18:47 [PATCH 0/2] hugetlb fixes Joern Engel
2013-06-18 18:47 ` [PATCH 1/2] hugetlb: properly account rss Joern Engel
2013-06-28 22:03 ` Andrew Morton
2013-07-03 13:41 ` Steve Capper
2013-07-03 14:55 ` Steve Capper
2013-06-18 18:47 ` [PATCH 2/2] mmap: allow MAP_HUGETLB for hugetlbfs files Joern Engel
2013-06-19 1:22 ` Jianguo Wu
2013-06-19 16:25 ` [PATCH] mmap: allow MAP_HUGETLB for hugetlbfs files v2 Jörn Engel
2013-06-20 1:31 ` Jianguo Wu
2013-06-19 16:25 ` [PATCH 2/2] mmap: allow MAP_HUGETLB for hugetlbfs files Jörn Engel
2013-06-18 18:50 ` [PATCH 0/2] hugetlb fixes Jörn Engel
2013-06-18 20:27 ` Andrew Morton
2013-06-18 20:04 ` Jörn Engel [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=20130618200433.GA28198@logfs.org \
--to=joern@logfs.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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