From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] io_setup.2: SYNOPSIS: return long
Date: Fri, 13 Nov 2020 10:24:30 +0100 [thread overview]
Message-ID: <3e4eee64-9c31-26c9-8bd0-a2cb9f782183@gmail.com> (raw)
In-Reply-To: <20201101135957.90237-1-colomar.6.4.3@gmail.com>
Hi Alex,
On 11/1/20 2:59 PM, Alejandro Colomar wrote:
> The Linux kernel uses a long as the return type for this syscall.
> As glibc provides no wrapper, use the same types the kernel uses.
>
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
Thanks. Patch applied.
Cheers,
Michael
> ---
>
> Hi Michael,
>
> Please apply this patch after "s/io_contexxt_t/aio_context_t/".
>
> Cheers,
>
> Alex
>
> man2/io_setup.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/io_setup.2 b/man2/io_setup.2
> index f9860fda5..1a89de220 100644
> --- a/man2/io_setup.2
> +++ b/man2/io_setup.2
> @@ -11,7 +11,7 @@ io_setup \- create an asynchronous I/O context
> .nf
> .BR "#include <linux/aio_abi.h>" " /* Defines needed types */"
> .PP
> -.BI "int io_setup(unsigned " nr_events ", aio_context_t *" ctx_idp );
> +.BI "long io_setup(unsigned " nr_events ", aio_context_t *" ctx_idp );
> .fi
> .PP
> .IR Note :
>
--
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:[~2020-11-13 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 13:59 [PATCH] io_setup.2: SYNOPSIS: return long Alejandro Colomar
2020-11-02 7:37 ` Michael Kerrisk (man-pages)
2020-11-02 12:20 ` Alejandro Colomar
2020-11-02 13:09 ` Michael Kerrisk (man-pages)
2020-11-02 13:12 ` Alejandro Colomar
2020-11-11 15:39 ` Ping: " Alejandro Colomar
2020-11-13 9:23 ` Michael Kerrisk (man-pages)
2020-11-13 9:24 ` 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=3e4eee64-9c31-26c9-8bd0-a2cb9f782183@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.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