linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, Andrea Arcangeli <aarcange@redhat.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Axel Rasmussen <axelrasmussen@google.com>,
	linux-kernel@vger.kernel.org,
	Linux MM Mailing List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Nadav Amit <nadav.amit@gmail.com>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: Re: [PATCH v3 4/4] ioctl_userfaultfd.2: Add write-protect mode docs
Date: Mon, 22 Mar 2021 18:06:36 -0400	[thread overview]
Message-ID: <20210322220636.GI16645@xz-x1> (raw)
In-Reply-To: <5c533ba3-f335-0681-223f-bf2202a9b72a@gmail.com>

On Fri, Mar 19, 2021 at 11:37:20PM +0100, Alejandro Colomar (man-pages) wrote:
> Hi Peter,

Hi, Alex,

> > +generate another write-protect userfault message.
> > +This is only used in conjunction with write-protect mode when both missing and
> 
> "when both missing"
> 
> both what?

I modified it to:

        This is only used when both
        .B UFFDIO_REGISTER_MODE_MISSING
        and
        .B UFFDIO_REGISTER_MODE_WP
        modes are enabled for the registered range.

And I fixed all the rest, including all the comments in patch 3.

Thanks for looking, I'll repost shortly.

-- 
Peter Xu



      reply	other threads:[~2021-03-22 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 22:22 [PATCH v3 0/4] man2: udpate mm/userfaultfd manpages to latest Peter Xu
2021-03-10 22:22 ` [PATCH v3 1/4] userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Peter Xu
2021-03-10 22:22 ` [PATCH v3 2/4] userfaultfd.2: Add write-protect mode Peter Xu
2021-03-19 22:25   ` Alejandro Colomar (man-pages)
2021-03-10 22:22 ` [PATCH v3 3/4] ioctl_userfaultfd.2: Add UFFD_FEATURE_THREAD_ID docs Peter Xu
2021-03-10 22:23 ` [PATCH v3 4/4] ioctl_userfaultfd.2: Add write-protect mode docs Peter Xu
2021-03-19 22:37   ` Alejandro Colomar (man-pages)
2021-03-22 22:06     ` Peter Xu [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=20210322220636.GI16645@xz-x1 \
    --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