From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Dave Hansen <dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux API <linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 1/5] pkey.7: New page with overview of Memory Protection Keys
Date: Tue, 18 Oct 2016 08:01:01 +0200 [thread overview]
Message-ID: <892b3bbe-f6c4-96f7-8db7-d0d257c78ab1@gmail.com> (raw)
In-Reply-To: <58054B48.1030600-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On 10/18/2016 12:06 AM, Dave Hansen wrote:
> On 10/17/2016 05:04 AM, Michael Kerrisk (man-pages) wrote:
>>> The 13 Sep version is the latest version of the man pages. Those fully
>>> describe the functionality that hit mainline and I haven't updated them
>>> since 13 Sep.
>>
>> Okay -- I've merged these pages. I did a fair bit of editing, mainly
>> wording fixes, and textual reorganization, but also adding a few
>> details that were missing. Could you take a look at the pkey_alloc(2),
>> mprotect(2), and pkeys(7) page that are currently in man-pages
>> Git and let me know if anything needs fixing, or if there are any
>> details that it occurs to you still need to be added.
>
> These look good, except for a bit of signal handing description that I
> neglected to send. I'll have a patch out for it momentarily.
>
Thanks for checking the pages!
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2016-10-18 6:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 19:44 [PATCH 0/5] [RFCv5] add manpages for Memory Protection Keys Dave Hansen
2016-09-13 19:44 ` [PATCH 1/5] pkey.7: New page with overview of " Dave Hansen
2016-10-12 6:25 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkj8voeBsjERrRq+17L9rK5Vy_quv7Dm_7Hkmuvxfpw_iQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-12 16:41 ` Dave Hansen
[not found] ` <57FE679D.8010101-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-10-17 12:04 ` Michael Kerrisk (man-pages)
[not found] ` <558d30e9-e374-728c-2099-ed8eccadf7a2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-10-17 22:06 ` Dave Hansen
[not found] ` <58054B48.1030600-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-10-18 6:01 ` Michael Kerrisk (man-pages) [this message]
2016-09-13 19:45 ` [PATCH 2/5] mprotect.2: add pkey_mprotect() syscall Dave Hansen
2016-09-13 19:45 ` [PATCH 3/5] pkey_alloc.2: New page describing protection key allocation and free Dave Hansen
2016-09-13 19:46 ` [PATCH 4/5] sigaction.2: describe siginfo changes from pkey-induced signals Dave Hansen
2016-09-13 19:46 ` [PATCH 5/5] proc.5: describe new ProtectionKey smaps field Dave Hansen
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=892b3bbe-f6c4-96f7-8db7-d0d257c78ab1@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dave.hansen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=x86-DgEjT+Ai2ygdnm+yROfE0A@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).