From: Alejandro Colomar <alx@kernel.org>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: Peter Xu <peterx@redhat.com>,
linux-man@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] userfaultfd man page updates
Date: Mon, 9 Oct 2023 00:27:25 +0200 [thread overview]
Message-ID: <ZSMszf3ASoQ8n6Hd@debian> (raw)
In-Reply-To: <20231003194547.2237424-1-axelrasmussen@google.com>
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
Hi Axel,
On Tue, Oct 03, 2023 at 12:45:42PM -0700, Axel Rasmussen wrote:
> This series includes only the remaining patches not applied from v1, with
> review comments addressed. This series is based on the "contrib" branch.
Thanks. For the next revision, I've moved the contrib branch to my
personal repo, since it's more of a personal branch. You can find it
here:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/log/?h=contrib>
Cheers,
Alex
>
> Changelog:
>
> v1->v2:
> - In patch 1 (patch 5 in v1), change "after" to "since" for consistency and to
> be clear that we mean 4.11+ (inclusive).
> - In patch 2 (patch 7 in v1), reorder error codes alphabetically (EINVAL then
> EPERM).
> - In patch 3 (patch 8 in v1), resolve conflicts with earlier review comments.
>
> Original cover letter:
>
> Various updates for userfaultfd man pages. To summarize the changes:
>
> - Correctly / fully describe the two-step feature support handshake process.
> - Describe new UFFDIO_POISON ioctl.
> - Other small improvements (missing ioctls, error codes, etc).
>
> Axel Rasmussen (5):
> ioctl_userfaultfd.2: describe two-step feature handshake
> ioctl_userfaultfd.2: correct and update UFFDIO_API ioctl error codes
> ioctl_userfaultfd.2: clarify the state of the uffdio_api structure on
> error
> ioctl_userfaultfd.2: fix / update UFFDIO_REGISTER error code list
> ioctl_userfaultfd.2: document new UFFDIO_POISON ioctl
>
> man2/ioctl_userfaultfd.2 | 226 +++++++++++++++++++++++++++++++--------
> 1 file changed, 181 insertions(+), 45 deletions(-)
>
> --
> 2.42.0.609.gbb76f46606-goog
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-10-08 22:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 19:45 [PATCH v2 0/5] userfaultfd man page updates Axel Rasmussen
2023-10-03 19:45 ` [PATCH v2 1/5] ioctl_userfaultfd.2: describe two-step feature handshake Axel Rasmussen
2023-10-08 22:23 ` Alejandro Colomar
2023-10-03 19:45 ` [PATCH v2 2/5] ioctl_userfaultfd.2: correct and update UFFDIO_API ioctl error codes Axel Rasmussen
2023-10-08 22:25 ` Alejandro Colomar
2023-10-03 19:45 ` [PATCH v2 3/5] ioctl_userfaultfd.2: clarify the state of the uffdio_api structure on error Axel Rasmussen
2023-10-08 21:52 ` Alejandro Colomar
2023-10-09 9:12 ` Mike Rapoport
2023-10-03 19:45 ` [PATCH v2 4/5] ioctl_userfaultfd.2: fix / update UFFDIO_REGISTER error code list Axel Rasmussen
2023-10-08 22:06 ` Alejandro Colomar
2023-10-17 21:23 ` Guillem Jover
2023-10-17 21:42 ` Alejandro Colomar
2023-10-17 22:14 ` Axel Rasmussen
2023-10-03 19:45 ` [PATCH v2 5/5] ioctl_userfaultfd.2: document new UFFDIO_POISON ioctl Axel Rasmussen
2023-10-08 22:23 ` Alejandro Colomar
2023-10-17 22:25 ` Axel Rasmussen
2023-10-08 22:27 ` Alejandro Colomar [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=ZSMszf3ASoQ8n6Hd@debian \
--to=alx@kernel.org \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.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.