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 5/5] userfaultfd.2: update VERSIONS section with 4.11 chanegs Date: Mon, 1 May 2017 20:33:56 +0200 [thread overview] Message-ID: <6ef50ec3-facc-104c-6787-567ece15e817@gmail.com> (raw) In-Reply-To: <1493617399-20897-6-git-send-email-rppt@linux.vnet.ibm.com> Hi Mike, On 05/01/2017 07:43 AM, Mike Rapoport wrote: > Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com> Thanks. Applied. Cheers, Michael > --- > man2/userfaultfd.2 | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2 > index f177bba..07a69f1 100644 > --- a/man2/userfaultfd.2 > +++ b/man2/userfaultfd.2 > @@ -404,6 +404,9 @@ Insufficient kernel memory was available. > The > .BR userfaultfd () > system call first appeared in Linux 4.3. > + > +The support for hugetlbfs and shared memory areas and > +non-page-fault events was added in Linux 4.11 > .SH CONFORMING TO > .BR userfaultfd () > is Linux-specific and should not be used in programs intended to be > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
WARNING: multiple messages have this Message-ID (diff)
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 5/5] userfaultfd.2: update VERSIONS section with 4.11 chanegs Date: Mon, 1 May 2017 20:33:56 +0200 [thread overview] Message-ID: <6ef50ec3-facc-104c-6787-567ece15e817@gmail.com> (raw) In-Reply-To: <1493617399-20897-6-git-send-email-rppt@linux.vnet.ibm.com> Hi Mike, On 05/01/2017 07:43 AM, Mike Rapoport wrote: > Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com> Thanks. Applied. Cheers, Michael > --- > man2/userfaultfd.2 | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2 > index f177bba..07a69f1 100644 > --- a/man2/userfaultfd.2 > +++ b/man2/userfaultfd.2 > @@ -404,6 +404,9 @@ Insufficient kernel memory was available. > The > .BR userfaultfd () > system call first appeared in Linux 4.3. > + > +The support for hugetlbfs and shared memory areas and > +non-page-fault events was added in Linux 4.11 > .SH CONFORMING TO > .BR userfaultfd () > is Linux-specific and should not be used in programs intended to be > -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- 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>
next prev parent reply other threads:[~2017-05-01 18:34 UTC|newest] Thread overview: 41+ 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 ` 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 5:43 ` Mike Rapoport 2017-05-01 18:33 ` Michael Kerrisk (man-pages) 2017-05-01 18:33 ` Michael Kerrisk (man-pages) 2017-05-02 9:31 ` Mike Rapoport 2017-05-02 9:31 ` Mike Rapoport 2017-05-02 9:31 ` Mike Rapoport 2017-05-02 20:23 ` Michael Kerrisk (man-pages) 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 5:43 ` Mike Rapoport 2017-05-01 18:33 ` Michael Kerrisk (man-pages) 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 5:43 ` Mike Rapoport 2017-05-01 18:33 ` Michael Kerrisk (man-pages) 2017-05-01 18:33 ` Michael Kerrisk (man-pages) 2017-05-02 9:32 ` Mike Rapoport 2017-05-02 9:32 ` Mike Rapoport 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 5:43 ` Mike Rapoport 2017-05-01 18:33 ` Michael Kerrisk (man-pages) 2017-05-01 18:33 ` Michael Kerrisk (man-pages) 2017-05-02 9:46 ` Mike Rapoport 2017-05-02 9:46 ` Mike Rapoport 2017-05-02 20:27 ` Michael Kerrisk (man-pages) 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 5:43 ` Mike Rapoport 2017-05-01 18:33 ` Michael Kerrisk (man-pages) [this message] 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-01 18:34 ` Michael Kerrisk (man-pages) 2017-05-02 9:48 ` Mike Rapoport 2017-05-02 9:48 ` Mike Rapoport 2017-05-02 20:28 ` Michael Kerrisk (man-pages) 2017-05-02 20:28 ` Michael Kerrisk (man-pages) 2017-05-02 20:28 ` 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=6ef50ec3-facc-104c-6787-567ece15e817@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: linkBe 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.