All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man2/userfaultfd.2: ffix
Date: Mon, 9 Oct 2023 00:45:37 +0200	[thread overview]
Message-ID: <ZSMxEqGwjmk1jDEz@debian> (raw)
In-Reply-To: <20231006064254.bsladknplzq5rurq@illithid>

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

Hi Branden,

On Fri, Oct 06, 2023 at 01:42:54AM -0500, G. Branden Robinson wrote:

Patch applied.  Should I amend with
`Signed-off-by: "G. Branden Robinson" <branden@debian.org>`?

Cheers,
Alex

> ---
>  man2/userfaultfd.2 | 9 ++++-----
>  1 file changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2
> index b2b79f61d..97f13cce9 100644
> --- a/man2/userfaultfd.2
> +++ b/man2/userfaultfd.2
> @@ -222,12 +222,11 @@ .SS Userfaultfd operation
>  a page fault occurring in the requested memory range, and satisfying
>  the mode defined at the registration time, will be forwarded by the kernel to
>  the user-space application.
> -The application can then use various (e.g.
> -.B UFFDIO_COPY ,
> -.B UFFDIO_ZEROPAGE ,
> +The application can then use various (e.g.,
> +.BR UFFDIO_COPY ,
> +.BR UFFDIO_ZEROPAGE ,
>  or
> -.B UFFDIO_CONTINUE
> -)
> +.BR UFFDIO_CONTINUE )
>  .BR ioctl (2)
>  operations to resolve the page fault.
>  .PP
> -- 
> 2.30.2



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

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

  reply	other threads:[~2023-10-08 22:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06  6:42 [PATCH] man2/userfaultfd.2: ffix G. Branden Robinson
2023-10-08 22:45 ` Alejandro Colomar [this message]
2023-10-08 22:55   ` G. Branden Robinson
2023-10-08 23:21     ` 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=ZSMxEqGwjmk1jDEz@debian \
    --to=alx@kernel.org \
    --cc=g.branden.robinson@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 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.