From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: Review request: draft ioctl_userfaultfd(2) manual page
Date: Tue, 25 Apr 2017 11:00:48 +0300 [thread overview]
Message-ID: <20170425080047.GA16770@rapoport-lnx> (raw)
In-Reply-To: <4c05c2bb-af77-d706-9455-8ceaa5510580@gmail.com>
Hello Michael,
On Fri, Apr 21, 2017 at 01:41:18PM +0200, Michael Kerrisk (man-pages) wrote:
> Hi Mike,
>
[...]
> >
> > Yes.
> > Just the future is only a week or two from today as we are at 4.11-rc7 :)
>
> Yes, I understand :-). So of course there's a *lot* more
> new stuff to document, right?
I've started to add the description of the new functionality to both
userfaultfd.2 and ioctl_userfaultfd.2 and it's somewhat difficult for me to
decide how it would be better to split the information between these two
pages and what should be the pages internal structure.
I even thought about possibility of adding relatively comprehensive
description of userfaultfd as man7/userfaultfd.7 and then keeping the pages
in man2 relatively small, just with brief description of APIs and SEE ALSO
pointing to man7.
Any advise is highly appreciated.
> [...]
--
Sincerely yours,
Mike.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: Review request: draft ioctl_userfaultfd(2) manual page
Date: Tue, 25 Apr 2017 11:00:48 +0300 [thread overview]
Message-ID: <20170425080047.GA16770@rapoport-lnx> (raw)
In-Reply-To: <4c05c2bb-af77-d706-9455-8ceaa5510580@gmail.com>
Hello Michael,
On Fri, Apr 21, 2017 at 01:41:18PM +0200, Michael Kerrisk (man-pages) wrote:
> Hi Mike,
>
[...]
> >
> > Yes.
> > Just the future is only a week or two from today as we are at 4.11-rc7 :)
>
> Yes, I understand :-). So of course there's a *lot* more
> new stuff to document, right?
I've started to add the description of the new functionality to both
userfaultfd.2 and ioctl_userfaultfd.2 and it's somewhat difficult for me to
decide how it would be better to split the information between these two
pages and what should be the pages internal structure.
I even thought about possibility of adding relatively comprehensive
description of userfaultfd as man7/userfaultfd.7 and then keeping the pages
in man2 relatively small, just with brief description of APIs and SEE ALSO
pointing to man7.
Any advise is highly appreciated.
> [...]
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2017-04-25 8:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 20:08 Review request: draft userfaultfd(2) manual page Michael Kerrisk (man-pages)
2017-03-20 20:08 ` Michael Kerrisk (man-pages)
2017-03-20 20:08 ` Michael Kerrisk (man-pages)
2017-03-20 20:11 ` Review request: draft ioctl_userfaultfd(2) " Michael Kerrisk (man-pages)
2017-03-20 20:11 ` Michael Kerrisk (man-pages)
2017-03-22 13:54 ` Mike Rapoport
2017-03-22 13:54 ` Mike Rapoport
2017-03-22 13:54 ` Mike Rapoport
2017-04-21 9:11 ` Michael Kerrisk (man-pages)
2017-04-21 9:11 ` Michael Kerrisk (man-pages)
2017-04-21 9:11 ` Michael Kerrisk (man-pages)
[not found] ` <e8c5ca4a-0710-7206-b96e-10d171bda218-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-04-21 11:07 ` Mike Rapoport
2017-04-21 11:07 ` Mike Rapoport
2017-04-21 11:07 ` Mike Rapoport
2017-04-21 11:41 ` Michael Kerrisk (man-pages)
2017-04-21 11:41 ` Michael Kerrisk (man-pages)
2017-04-21 11:41 ` Michael Kerrisk (man-pages)
2017-04-25 8:00 ` Mike Rapoport [this message]
2017-04-25 8:00 ` Mike Rapoport
2017-04-25 10:59 ` Michael Kerrisk (man-pages)
2017-04-25 10:59 ` Michael Kerrisk (man-pages)
2017-04-25 10:59 ` Michael Kerrisk (man-pages)
2017-05-03 21:46 ` Andrea Arcangeli
2017-05-03 21:46 ` Andrea Arcangeli
2017-05-03 21:46 ` Andrea Arcangeli
2017-03-21 14:01 ` Review request: draft userfaultfd(2) " Mike Rapoport
2017-03-21 14:01 ` Mike Rapoport
2017-03-21 14:01 ` Mike Rapoport
2017-04-21 6:30 ` Michael Kerrisk (man-pages)
2017-04-21 6:30 ` Michael Kerrisk (man-pages)
2017-04-21 6:30 ` Michael Kerrisk (man-pages)
2017-04-21 11:06 ` Mike Rapoport
2017-04-21 11:06 ` Mike Rapoport
2017-04-21 11:06 ` Mike Rapoport
2017-04-21 11:30 ` Michael Kerrisk (man-pages)
2017-04-21 11:30 ` Michael Kerrisk (man-pages)
2017-04-21 11:30 ` Michael Kerrisk (man-pages)
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=20170425080047.GA16770@rapoport-lnx \
--to=rppt@linux.vnet.ibm.com \
--cc=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.