From: Alejandro Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] memchr.3: rawmemchr doesn't have an n parameter
Date: Sat, 8 Jul 2023 18:02:31 +0200 [thread overview]
Message-ID: <a02eb61b-e5ae-71f9-0eea-14d77729d768@gmail.com> (raw)
In-Reply-To: <etk3j3tom3mzgm43gm5bpiwrittjrpf6zriqikhw2xsej6ltse@3gnfru2czeyu>
[-- Attachment #1.1: Type: text/plain, Size: 981 bytes --]
On 6/23/23 18:54, наб wrote:
> The /point/ is it's unbounded;
> git grep -F 'void "' | grep -F '[]'
> didn't return anything so I reverted it to a void*.
>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
Oops, my bad. Patch applied. Thanks,
Alex
> man3/memchr.3 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man3/memchr.3 b/man3/memchr.3
> index e2916dc9a..030806aa0 100644
> --- a/man3/memchr.3
> +++ b/man3/memchr.3
> @@ -23,7 +23,7 @@ .SH SYNOPSIS
> .BI "void *memchr(const void " s [. n "], int " c ", size_t " n );
> .BI "void *memrchr(const void " s [. n "], int " c ", size_t " n );
> .PP
> -.BI "[[deprecated]] void *rawmemchr(const void " s [. n "], int " c );
> +.BI "[[deprecated]] void *rawmemchr(const void *" s ", int " c );
> .fi
> .PP
> .RS -4
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-07-08 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 16:54 [PATCH] memchr.3: rawmemchr doesn't have an n parameter наб
2023-07-08 16:02 ` 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=a02eb61b-e5ae-71f9-0eea-14d77729d768@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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