From: Vlastimil Babka <vbabka-AlSwsSmVLrQ@public.gmane.org>
To: Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Eric B Munson <emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] mlock.2: mlock2.2: Add entry to for new mlock2 syscall
Date: Wed, 9 Sep 2015 14:00:53 +0200 [thread overview]
Message-ID: <55F01F75.8080706@suse.cz> (raw)
In-Reply-To: <20150831092300.GE29723-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
On 08/31/2015 11:23 AM, Michal Hocko wrote:
> On Fri 28-08-15 14:43:11, Eric B Munson wrote:
>> Update the mlock.2 man page with information on mlock2() and the new
>> mlockall() flag MCL_ONFAULT.
>>
>> Signed-off-by: Eric B Munson <emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
>> Cc: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>
>
> Acked-by: Michal Hocko <mhocko-IBi9RG/b67k@public.gmane.org>
Acked-by: Vlastimil Babka <vbabka-AlSwsSmVLrQ@public.gmane.org>
>
> I am not familiar with the format much so I am just looking at the text
> and that looks reasonable to me.
Same here.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-09-09 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 18:43 [PATCH] mlock.2: mlock2.2: Add entry to for new mlock2 syscall Eric B Munson
[not found] ` <1440787391-30298-1-git-send-email-emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2015-08-28 18:47 ` Eric B Munson
2015-08-31 9:23 ` Michal Hocko
[not found] ` <20150831092300.GE29723-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2015-09-09 12:00 ` Vlastimil Babka [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=55F01F75.8080706@suse.cz \
--to=vbabka-alswssmvlrq@public.gmane.org \
--cc=corbet-T1hC0tSOHrs@public.gmane.org \
--cc=emunson-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).