From: Peter Xu <peterx@redhat.com>
To: linux-man@vger.kernel.org
Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>,
Nadav Amit <nadav.amit@gmail.com>,
linux-kernel@vger.kernel.org,
Linux MM Mailing List <linux-mm@kvack.org>,
peterx@redhat.com, Axel Rasmussen <axelrasmussen@google.com>,
Alejandro Colomar <alx.manpages@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: [PATCH 0/4] man2: udpate mm/userfaultfd manpages to latest
Date: Wed, 3 Mar 2021 20:59:43 -0500 [thread overview]
Message-ID: <20210304015947.517713-1-peterx@redhat.com> (raw)
There're two features missing in current manpage, namely:
(1) Userfaultfd Thread-ID feature
(2) Userfaultfd write protect mode
There's also a 3rd one which was just contributed from Axel - Axel, I think it
would be great if you can add that part too, probably after the whole
hugetlbfs/shmem minor mode reaches the linux master branch.
Please review, thanks.
Peter Xu (4):
userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs
userfaultfd.2: Add write-protect mode
ioctl_userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs
ioctl_userfaultfd.2: Add write-protect mode docs
man2/ioctl_userfaultfd.2 | 76 +++++++++++++++++++++++++++--
man2/userfaultfd.2 | 100 ++++++++++++++++++++++++++++++++++++++-
2 files changed, 171 insertions(+), 5 deletions(-)
--
2.26.2
next reply other threads:[~2021-03-04 1:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 1:59 Peter Xu [this message]
2021-03-04 1:59 ` [PATCH 1/4] userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Peter Xu
2021-03-04 6:38 ` Mike Rapoport
2021-03-04 15:53 ` Peter Xu
2021-03-04 9:22 ` Alejandro Colomar (man-pages)
2021-03-04 15:50 ` Peter Xu
2021-03-04 18:13 ` Alejandro Colomar (man-pages)
2021-03-04 1:59 ` [PATCH 2/4] userfaultfd.2: Add write-protect mode Peter Xu
2021-03-04 6:46 ` Mike Rapoport
2021-03-04 16:02 ` Peter Xu
2021-03-04 1:59 ` [PATCH 3/4] ioctl_userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Peter Xu
2021-03-04 1:59 ` [PATCH 4/4] ioctl_userfaultfd.2: Add write-protect mode docs Peter Xu
2021-03-04 16:12 ` Peter Xu
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=20210304015947.517713-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alx.manpages@gmail.com \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=nadav.amit@gmail.com \
--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