From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
Vineet Gupta <vgupta@synopsys.com>,
linux-snps-arc@lists.infradead.org,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Guo Ren <guoren@kernel.org>,
linux-csky@vger.kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, Nick Hu <nickhu@andestech.com>,
Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>,
libc-alpha@sourceware.org, Dave Martin <Dave.Martin@arm.com>,
Martin Sebor <msebor@redhat.com>
Subject: Re: [PATCH] cacheflush.2: Update SYNOPSIS for glibc wrapper
Date: Sun, 17 Jan 2021 21:55:44 +0100 [thread overview]
Message-ID: <05679e0d-c716-419d-d3e3-c4ae46446dcb@gmail.com> (raw)
In-Reply-To: <1c234bd5-306a-7496-fd3d-268f46450168@gmail.com>
On 1/17/21 9:43 PM, Alejandro Colomar (man-pages) wrote:
> Hi Michael,
>
> On 1/17/21 9:34 PM, Michael Kerrisk (man-pages) wrote:
>> Hi Alex,
>>
>> On 1/16/21 3:56 PM, Alejandro Colomar wrote:
>>> Glibc uses 'void *' instead of 'char *'.
>>> And the prototype is declared in <sys/cacheflush.h>.
>
> D'oh!
>
>>>
>>> ......
>>>
>>> $ syscall='cacheflush';
>>> $ ret='int';
>>> $ find glibc/ -type f -name '*.h' \
>>> |xargs pcregrep -Mn "(?s)^[\w\s]*${ret}\s*${syscall}\s*\(.*?;";
>>> glibc/sysdeps/unix/sysv/linux/nios2/sys/cachectl.h:27:
>
> It is defined in <sys/cachectl.h>
>
> Please fix that.
Fixed! (Everything pushed now.)
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2021-01-17 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 14:56 [PATCH] cacheflush.2: Update SYNOPSIS for glibc wrapper Alejandro Colomar
2021-01-17 20:34 ` Michael Kerrisk (man-pages)
2021-01-17 20:43 ` Alejandro Colomar (man-pages)
2021-01-17 20:55 ` Michael Kerrisk (man-pages) [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=05679e0d-c716-419d-d3e3-c4ae46446dcb@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=Dave.Martin@arm.com \
--cc=alx.manpages@gmail.com \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=guoren@kernel.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=msebor@redhat.com \
--cc=nickhu@andestech.com \
--cc=tsbogend@alpha.franken.de \
--cc=vgupta@synopsys.com \
--cc=xypron.glpk@gmx.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