From: Alejandro Colomar <alx.mailinglists@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] mmap.2: ffix
Date: Sun, 27 Feb 2022 18:09:51 +0100 [thread overview]
Message-ID: <75bc59ef-6a3e-1539-dcc3-6c6a2a411e85@gmail.com> (raw)
In-Reply-To: <20211112103938.3888-1-jwilk@jwilk.net>
Hi, Jakub and Branden!
On 11/12/21 11:39, Jakub Wilk wrote:
> '" type of behavior:' was incorrectly formatted in bold.
Thanks for the report!
>
> Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
> ---
> man2/mmap.2 | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/man2/mmap.2 b/man2/mmap.2
> index 96b7444b0..f6e406ed5 100644
> --- a/man2/mmap.2
> +++ b/man2/mmap.2
> @@ -289,8 +289,7 @@ Note that older kernels which do not recognize the
> .BR MAP_FIXED_NOREPLACE
> flag will typically (upon detecting a collision with a preexisting mapping)
> fall back to a "non-\c
> -.B MAP_FIXED\c
> -" type of behavior:
Branden, why is that? Is a leading '"' special here?
> +.BR MAP_FIXED "\(dq type of behavior:"
I'll apply a slightly simpler patch (removing \c):
diff --git a/man2/mmap.2 b/man2/mmap.2
index 30756f078..d0291be8e 100644
--- a/man2/mmap.2
+++ b/man2/mmap.2
@@ -271,9 +271,9 @@ one thread will succeed; all others will report failure.
Note that older kernels which do not recognize the
.BR MAP_FIXED_NOREPLACE
flag will typically (upon detecting a collision with a preexisting mapping)
-fall back to a "non-\c
-.B MAP_FIXED\c
-" type of behavior:
+fall back to a
+.RB \(dqnon- MAP_FIXED \(dq
+type of behavior:
they will return an address that is different from the requested address.
Therefore, backward-compatible software
should check the returned address against the requested address.
> they will return an address that is different from the requested address.
> Therefore, backward-compatible software
> should check the returned address against the requested address.
--
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-02-27 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 10:39 [PATCH] mmap.2: ffix Jakub Wilk
2022-02-27 17:09 ` Alejandro Colomar [this message]
2022-02-27 18:57 ` G. Branden Robinson
2022-02-27 19:02 ` Alejandro Colomar (man-pages)
2022-02-28 13:18 ` G. Branden Robinson
2022-02-28 15:11 ` Alejandro Colomar (man-pages)
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=75bc59ef-6a3e-1539-dcc3-6c6a2a411e85@gmail.com \
--to=alx.mailinglists@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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