linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Axel Rasmussen <axelrasmussen@google.com>
To: Alejandro Colomar <alx@kernel.org>,
	Mike Rapoport <rppt@kernel.org>, Peter Xu <peterx@redhat.com>
Cc: linux-man@vger.kernel.org, linux-mm@kvack.org,
	 linux-kernel@vger.kernel.org,
	Axel Rasmussen <axelrasmussen@google.com>
Subject: [PATCH v3 0/3] userfaultfd man page updates
Date: Tue, 17 Oct 2023 16:01:07 -0700	[thread overview]
Message-ID: <20231017230110.3170850-1-axelrasmussen@google.com> (raw)

This series includes only the remaining patches not applied from v1/v2,
with review comments addressed. This series is based on the "contrib"
branch [1].

Changelog:

v2->v3:
 - Rebased onto updated contrib branch.
 - In patch 2 (patch 4 in v2), reordered error codes in alphabetical order,
   and fixed extra spacing in the EINVAL error description.
 - In patch 3, fix mistakenly copy-pasted "struct uffdio_continue" (should
   have been "struct uffdio_poison"), and alphabetically order
   UFFDIO_CONTINUE error codes.

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).

[1]: https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/log/?h=contrib

Axel Rasmussen (3):
  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 | 173 ++++++++++++++++++++++++++++++++-------
 1 file changed, 145 insertions(+), 28 deletions(-)

--
2.42.0.655.g421f12c284-goog



             reply	other threads:[~2023-10-17 23:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 23:01 Axel Rasmussen [this message]
2023-10-17 23:01 ` [PATCH v3 1/3] ioctl_userfaultfd.2: clarify the state of the uffdio_api structure on error Axel Rasmussen
2023-10-17 23:07   ` Alejandro Colomar
2023-10-17 23:01 ` [PATCH v3 2/3] ioctl_userfaultfd.2: fix / update UFFDIO_REGISTER error code list Axel Rasmussen
2023-10-17 23:23   ` Alejandro Colomar
2023-10-17 23:01 ` [PATCH v3 3/3] ioctl_userfaultfd.2: document new UFFDIO_POISON ioctl Axel Rasmussen
2023-10-17 23:20   ` Alejandro Colomar

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=20231017230110.3170850-1-axelrasmussen@google.com \
    --to=axelrasmussen@google.com \
    --cc=alx@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.com \
    --cc=rppt@kernel.org \
    /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