From: Alejandro Colomar <alx.manpages@gmail.com>
To: Tom Schwindl <schwindl@posteo.de>
Cc: linux-man@vger.kernel.org,
"G. Branden Robinson" <g.branden.robinson@gmail.com>,
Jakub Wilk <jwilk@jwilk.net>, Alejandro Colomar <alx@kernel.org>
Subject: Re: [PATCH] memcmp.3: wfix
Date: Wed, 15 Feb 2023 18:41:05 +0100 [thread overview]
Message-ID: <afd54ed3-c044-844c-ce86-d3633d498c6b@gmail.com> (raw)
In-Reply-To: <20230215173343.30846-1-schwindl@posteo.de>
[-- Attachment #1.1: Type: text/plain, Size: 921 bytes --]
Hi Tom,
On 2/15/23 18:33, Tom Schwindl wrote:
> Signed-off-by: Tom Schwindl <schwindl@posteo.de>
Patch applied. Thanks!
Cheers,
Alex
> ---
> man3/memcmp.3 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man3/memcmp.3 b/man3/memcmp.3
> index c2427a00ac12..de712bd0ae13 100644
> --- a/man3/memcmp.3
> +++ b/man3/memcmp.3
> @@ -73,7 +73,7 @@ Instead, a function that performs comparisons in constant time is required.
> Some operating systems provide such a function (e.g., NetBSD's
> .BR consttime_memequal ()),
> but no such function is specified in POSIX.
> -On Linux, it may be necessary to implement such a function oneself.
> +On Linux, you may need to implement such a function yourself.
> .SH SEE ALSO
> .BR bstring (3),
> .BR strcasecmp (3),
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-15 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 17:33 [PATCH] memcmp.3: wfix Tom Schwindl
2023-02-15 17:41 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-15 13:07 Tom Schwindl
2023-02-15 15:18 ` G. Branden Robinson
2023-02-15 16:11 ` Tom Schwindl
2023-02-15 17:00 ` Alejandro Colomar
2023-02-15 17:17 ` Jakub Wilk
2023-02-15 17:26 ` 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=afd54ed3-c044-844c-ce86-d3633d498c6b@gmail.com \
--to=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=schwindl@posteo.de \
/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