public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jesse Rosenstock <jrosenstock@google.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH] mmap.2: wfix
Date: Fri, 3 Jun 2022 18:25:22 +0200	[thread overview]
Message-ID: <a06413f0-c87d-f80e-cb3a-e27258fbcd59@gmail.com> (raw)
In-Reply-To: <CAMZQ0rKYpg6+4WD45BdEdPy1QiKtk+KbJL6WRZo9tVQ2B2qGXA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2166 bytes --]

Hi Jesse,

On 6/3/22 16:45, Jesse Rosenstock wrote:
> Change "supported only since" to "support was added in".
> 
> Previously, this said, "MAP_POPULATE is supported for private mappings only
> since Linux 2.6.23."  This could be parsed as "MAP_POPULATE is supported
> for private mappings only [not shared mappings] since Linux 2.6.23."
> Someone (a native English speaker) tried to tell me this.
> 
> Change to "Support for MAP_POPULATE in conjunction with private mappings
> was added in Linux 2.6.23."  This is unambiguous, and "support was
> added" is more common in other man pages.
> 
> There are more instances of "supported only since", but they seem
> clearer.  I could send a separate patch for them if desired.
> 
> Signed-off-by: Jesse Rosenstock <jmr@google.com>

The patch makes sense to me.  If you consider other patches would be 
good too, send them and I'll have a look at them.

Patch applied.

Thanks,

Alex

> ---
>   man2/mmap.2 | 7 ++++---
>   1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/man2/mmap.2 b/man2/mmap.2
> index 96b7444b0..b9cfe82a6 100644
> --- a/man2/mmap.2
> +++ b/man2/mmap.2
> @@ -215,11 +215,11 @@ The
>   argument should be zero.
>   .\" See the pgoff overflow check in do_mmap().
>   .\" See the offset check in sys_mmap in arch/x86/kernel/sys_x86_64.c.
> -The use of
> +Support for
>   .B MAP_ANONYMOUS
>   in conjunction with
>   .B MAP_SHARED
> -is supported on Linux only since kernel 2.4.
> +was added in Linux 2.4.
>   .TP
>   .B MAP_DENYWRITE
>   This flag is ignored.
> @@ -405,8 +405,9 @@ The
>   call doesn't fail if the mapping cannot be populated (for example, due
>   to limitations on the number of mapped huge pages when using
>   .BR MAP_HUGETLB ).
> +Support for
>   .BR MAP_POPULATE
> -is supported for private mappings only since Linux 2.6.23.
> +in conjunction with private mappings was added in Linux 2.6.23.
>   .TP
>   .BR MAP_STACK " (since Linux 2.6.27)"
>   Allocate the mapping at an address suitable for a process
> --
> 2.36.1.255.ge46751e96f-goog

-- 
Alejandro Colomar
<http://www.alejandro-colomar.es/>

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

      reply	other threads:[~2022-06-03 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 14:45 [PATCH] mmap.2: wfix Jesse Rosenstock
2022-06-03 16:25 ` 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=a06413f0-c87d-f80e-cb3a-e27258fbcd59@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=jrosenstock@google.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