From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: mtk.manpages@gmail.com, Andrea Arcangeli <aarcange@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-man@vger.kernel.org
Subject: Re: [PATCH man-pages 0/5] {ioctl_}userfaultfd.2: yet another update
Date: Tue, 2 May 2017 22:28:56 +0200 [thread overview]
Message-ID: <2bd667b5-35d1-6e7f-3f8f-5b4e163618a7@gmail.com> (raw)
In-Reply-To: <20170502094836.GD5910@rapoport-lnx>
On 05/02/2017 11:48 AM, Mike Rapoport wrote:
> On Mon, May 01, 2017 at 08:34:07PM +0200, Michael Kerrisk (man-pages) wrote:
>> Hi Mike,
>>
>> On 05/01/2017 07:43 AM, Mike Rapoport wrote:
>>> Hi Michael,
>>>
>>> These updates pretty much complete the coverage of 4.11 additions, IMHO.
>>
>> Thanks for this, but we still await input from Andrea
>> on various points.
>>
>>> Mike Rapoport (5):
>>> ioctl_userfaultfd.2: update description of shared memory areas
>>> ioctl_userfaultfd.2: UFFDIO_COPY: add ENOENT and ENOSPC description
>>> ioctl_userfaultfd.2: add BUGS section
>>> userfaultfd.2: add note about asynchronios events delivery
>>> userfaultfd.2: update VERSIONS section with 4.11 chanegs
>>>
>>> man2/ioctl_userfaultfd.2 | 35 +++++++++++++++++++++++++++++++++--
>>> man2/userfaultfd.2 | 15 +++++++++++++++
>>> 2 files changed, 48 insertions(+), 2 deletions(-)
>>
>> I've applied all of the above, and done some light editing.
>>
>> Could you please check my changes in the following commits:
>>
>> 5191c68806c8ac73fdc89586cde434d2766abb5c
>> 265225c1e2311ae26ead116e6c8d2cedd46144fa
>
> Both are Ok
> Reviewed-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
Thanks for checking, Mike.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2017-05-02 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 5:43 [PATCH man-pages 0/5] {ioctl_}userfaultfd.2: yet another update Mike Rapoport
2017-05-01 5:43 ` [PATCH man-pages 1/5] ioctl_userfaultfd.2: update description of shared memory areas Mike Rapoport
2017-05-01 18:33 ` Michael Kerrisk (man-pages)
2017-05-02 9:31 ` Mike Rapoport
2017-05-02 20:23 ` Michael Kerrisk (man-pages)
2017-05-01 5:43 ` [PATCH man-pages 2/5] ioctl_userfaultfd.2: UFFDIO_COPY: add ENOENT and ENOSPC description Mike Rapoport
2017-05-01 18:33 ` Michael Kerrisk (man-pages)
2017-05-01 5:43 ` [PATCH man-pages 3/5] ioctl_userfaultfd.2: add BUGS section Mike Rapoport
2017-05-01 18:33 ` Michael Kerrisk (man-pages)
2017-05-02 9:32 ` Mike Rapoport
2017-05-01 5:43 ` [PATCH man-pages 4/5] userfaultfd.2: add note about asynchronios events delivery Mike Rapoport
2017-05-01 18:33 ` Michael Kerrisk (man-pages)
2017-05-02 9:46 ` Mike Rapoport
2017-05-02 20:27 ` Michael Kerrisk (man-pages)
2017-05-01 5:43 ` [PATCH man-pages 5/5] userfaultfd.2: update VERSIONS section with 4.11 chanegs Mike Rapoport
2017-05-01 18:33 ` Michael Kerrisk (man-pages)
2017-05-01 18:34 ` [PATCH man-pages 0/5] {ioctl_}userfaultfd.2: yet another update Michael Kerrisk (man-pages)
2017-05-02 9:48 ` Mike Rapoport
2017-05-02 20:28 ` Michael Kerrisk (man-pages) [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=2bd667b5-35d1-6e7f-3f8f-5b4e163618a7@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.vnet.ibm.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 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).