[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150708100008.e8a000ec.akpm@linux-foundation.org>
Date: Wed, 8 Jul 2015 10:00:08 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Eric B Munson <emunson@...mai.com>
Cc: Shuah Khan <shuahkh@....samsung.com>,
Michal Hocko <mhocko@...e.cz>,
Michael Kerrisk <mtk.manpages@...il.com>,
Vlastimil Babka <vbabka@...e.cz>, linux-alpha@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org,
linux-parisc@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
sparclinux@...r.kernel.org, linux-xtensa@...ux-xtensa.org,
linux-mm@...ck.org, linux-arch@...r.kernel.org,
linux-api@...r.kernel.org
Subject: Re: [PATCH V3 0/5] Allow user to request memory to be locked on
page fault
On Wed, 8 Jul 2015 09:23:02 -0400 Eric B Munson <emunson@...mai.com> wrote:
> > I don't know whether these syscalls should be documented via new
> > manpages, or if we should instead add them to the existing
> > mlock/munlock/mlockall manpages. Michael, could you please advise?
> >
>
> Thanks for adding the series. I owe you several updates (getting the
> new syscall right for all architectures and a set of tests for the new
> syscalls). Would you prefer a new pair of patches or I update this set?
It doesn't matter much. I guess a full update will be more convenient
at your end.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists