From: Alejandro Colomar <alx@kernel.org>
To: Peter Xu <peterx@redhat.com>
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>,
Mike Rapoport <rppt@kernel.org>,
Axel Rasmussen <axelrasmussen@google.com>,
Kyle Huey <me@kylehuey.com>,
linux-mm@kvack.org, Robert O'Callahan <robert@ocallahan.org>,
Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH 1/2] UFFDIO_API.2const: Update userfaultfd handshake and feature probe
Date: Wed, 14 May 2025 20:34:22 +0200 [thread overview]
Message-ID: <5ttjhxdolfulke72aqi25tv5gfww7jl2cwtwgp6lu4zp66hl3d@kwowsvdhuju7> (raw)
In-Reply-To: <aCTRDSCSiRrswEXP@x1.local>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
Hi Peter,
On Wed, May 14, 2025 at 01:21:17PM -0400, Peter Xu wrote:
> On Wed, May 14, 2025 at 05:59:48PM +0200, Alejandro Colomar wrote:
> > > +.P
> > > +For historical reasons,
> > > +a temporary userfaultfd is needed to probe
> > > +what userfaultfd features the kernel supports.
> > > +The application needs to create a temporary userfaultfd,
> > > +issue an
> > > +.B UFFDIO_API
> > > +ioctl with
> > > +.I features
> > > +set to 0. After the
> >
> > Please use semantic newlines. Break the line after the '.'.
>
> This one was overlooked indeed, will fix it.
Thanks!
> >
> > $ MANWIDTH=72 man man-pages | sed -n '/Use semantic newlines/,/^$/p'
> > Use semantic newlines
> > In the source of a manual page, new sentences should be started
> > on new lines, long sentences should be split into lines at
> > clause breaks (commas, semicolons, colons, and so on), and long
> > clauses should be split at phrase boundaries. This convention,
> > sometimes known as "semantic newlines", makes it easier to see
> > the effect of patches, which often operate at the level of indi‐
> > vidual sentences, clauses, or phrases.
> >
> > Also, please say "zero" instead of "0", as was in the old paragraph.
> > That will allow git-diff(1) --color-moved to detect some movement of
> > text.
>
> This was not part of the old text, but sure, will do.
I know you've completely rewritten the paragraph, but even then, parts
of the old text remain (maybe because however you write it, some parts
need to be said).
-.I features
-field set to zero.
This part is kept in the new text, even if just by chance, and it might
be interesting to see that in git-diff(1) --color-moved.
Have a lovely day!
Alex
>
> Thanks,
>
> --
> Peter Xu
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-05-14 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 17:19 [PATCH 0/2] UFFDIO_API.2const: Two man page updates Peter Xu
2025-05-12 17:19 ` [PATCH 1/2] UFFDIO_API.2const: Update userfaultfd handshake and feature probe Peter Xu
2025-05-13 17:54 ` Kyle Huey
2025-05-14 15:59 ` Alejandro Colomar
2025-05-14 17:21 ` Peter Xu
2025-05-14 18:34 ` Alejandro Colomar [this message]
2025-05-12 17:19 ` [PATCH 2/2] UFFDIO_API.2const: Add an entry for UFFDIO_MOVE Peter Xu
2025-05-12 17:34 ` Suren Baghdasaryan
2025-05-14 15:02 ` Alejandro Colomar
2025-05-14 17:22 ` Peter Xu
2025-05-14 18:35 ` 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=5ttjhxdolfulke72aqi25tv5gfww7jl2cwtwgp6lu4zp66hl3d@kwowsvdhuju7 \
--to=alx@kernel.org \
--cc=aarcange@redhat.com \
--cc=axelrasmussen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=me@kylehuey.com \
--cc=peterx@redhat.com \
--cc=robert@ocallahan.org \
--cc=rppt@kernel.org \
--cc=surenb@google.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