Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Ethan Ferguson <ethanf108@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] Changed wording in userfaultfd.2
Date: Sat, 26 Sep 2026 15:14:43 +0200	[thread overview]
Message-ID: <arfFMMOrtYwfEqnc@debian> (raw)
In-Reply-To: <20260925172440.24358-1-ethan.ferguson@str.us>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

Hi Ethan,

> Date: 2026-09-25 13:24:40-0400
> From: Ethan Ferguson <ethanf108@gmail.com>
>
> From: Ethan Ferguson <ethanf108@gmail.com>
> 
> A fourth userfaultfd mode was added in commit aa7589c9ffce, but this
> wording wasn't changed.
> 
> Signed-off-by: Ethan Ferguson <ethanf108@gmail.com>
> 
> ---

Thanks!  I've applied the patch.  Have a lovely day!
Alex

>  man/man2/userfaultfd.2 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man/man2/userfaultfd.2 b/man/man2/userfaultfd.2
> index 23ae53890..c765b64c0 100644
> --- a/man/man2/userfaultfd.2
> +++ b/man/man2/userfaultfd.2
> @@ -75,7 +75,7 @@ all memory ranges that were registered with the object are unregistered
>  and unread events are flushed.
>  .\"
>  .P
> -Userfaultfd supports three modes of registration:
> +Userfaultfd supports four modes of registration:
>  .TP
>  .BR UFFDIO_REGISTER_MODE_MISSING " (since Linux 4.10)"
>  When registered with
> 
> base-commit: 227f4c2fd6c421ad8e4f81ccf1acad1a139fe3a7
> -- 
> 2.55.0
> 
> 

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-09-26 13:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 17:24 [PATCH] Changed wording in userfaultfd.2 Ethan Ferguson
2026-09-26 13:14 ` 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=arfFMMOrtYwfEqnc@debian \
    --to=alx@kernel.org \
    --cc=ethanf108@gmail.com \
    --cc=linux-man@vger.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