From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: Mike Rapoport <rppt@kernel.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Peter Xu <peterx@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
linux-man@vger.kernel.org, Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v2] ioctl_userfaultfd.2, userfaultfd.2: add minor fault mode
Date: Sat, 2 Apr 2022 23:48:51 +0200 [thread overview]
Message-ID: <cb85e759-d272-e165-beee-b0d1c8f87405@gmail.com> (raw)
In-Reply-To: <CAJHvVcggpJ7hE8VbhL09mT0=eJ5C+iH1poi_-V2v_dMLjSbVnQ@mail.gmail.com>
Hi Axel,
On 3/22/22 17:31, Axel Rasmussen wrote:
> On Mon, Aug 2, 2021 at 5:21 AM Alejandro Colomar (man-pages)
> <alx.manpages@gmail.com> wrote:
>>>>> +mode, user-space will receive a page-fault notification
>>
>> s/user-space/user space/
>>
>> See the following extract from man-pages(7):
>>
>> Preferred terms
>> The following table lists some preferred terms to use in
>> man pages, mainly to ensure consistency across pages.
>>
>> Term Avoid using Notes
>> ─────────────────────────────────────────────────────────────
>> [...]
>> user space userspace
>>
>> However, when user space is used as an adjective, per the usual English
>> rules, we write "user-space". Example: "a user-space program".
>
> 100% agreed that "user space" is more correct, but this man page
> already has many instances of "user-space" in it. I'd suggest we
> either fix all of them, or just follow the existing convention within
> this page.
>
> How about, leaving this as-is for this patch, to keep the diff tidy,
> and I can send a follow-up patch to fix all the instances of this in
> this page?
>
Sure. Sorry for the delay.
Thanks,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2022-04-02 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 19:56 [PATCH v2] ioctl_userfaultfd.2, userfaultfd.2: add minor fault mode Axel Rasmussen
2021-07-27 16:32 ` Axel Rasmussen
2021-08-02 11:21 ` Mike Rapoport
2021-08-02 12:21 ` Alejandro Colomar (man-pages)
2022-03-22 16:31 ` Axel Rasmussen
2022-04-02 21:48 ` Alejandro Colomar (man-pages) [this message]
2021-07-27 16:37 ` Peter Xu
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=cb85e759-d272-e165-beee-b0d1c8f87405@gmail.com \
--to=alx.manpages@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=mtk.manpages@gmail.com \
--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 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.