From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Ping: Re: [PATCH] io_setup.2: SYNOPSIS: return long
Date: Wed, 11 Nov 2020 16:39:24 +0100 [thread overview]
Message-ID: <e2463d0c-9fa7-6e8e-3adf-0439408f2593@gmail.com> (raw)
In-Reply-To: <7bba6ced-14f5-75af-933f-73eac0284a39@gmail.com>
Ping.
On 11/2/20 2:12 PM, Alejandro Colomar wrote:
>
>
> On 2020-11-02 14:09, Michael Kerrisk (man-pages) wrote:
>> Hi Alex,
>>
>> On Mon, 2 Nov 2020 at 13:20, Alejandro Colomar
>> <colomar.6.4.3@gmail.com> wrote:
>>>
>>> On 2020-11-02 08:37, Michael Kerrisk (man-pages) wrote:
>>> > 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.
>>> >
>>> > I think we need this patch for all of the io* pages, right?
>>>
>>> Hi Michael,
>>>
>>> For some reason, no. AFAICS, only io_setup() really uses 'long'.
>>
>> But is not SYSCALL_DEFINEX() producing a prototype with return value
>> 'long' in all the cases? (I have not checked, I just presume so.)
>
> Hi Michael,
>
> Well, yes.
> SYSCALL_DEFINEx() produces a return type of long
> for _all_ syscalls, AFAICS.
> (as I said before, that macro is a bit obscure, but I can read that).
>
> Would you like to change all syscall man pages (without a wrapper)
> to use long as the return type?
>
> Thanks.
>
> Alex
>
>>
>> Thanks,
>>
>> Michael
>>
>>
>>
>>
next prev parent reply other threads:[~2020-11-11 15:39 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 ` Alejandro Colomar [this message]
2020-11-13 9:23 ` Michael Kerrisk (man-pages)
2020-11-13 9:24 ` Michael Kerrisk (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=e2463d0c-9fa7-6e8e-3adf-0439408f2593@gmail.com \
--to=colomar.6.4.3@gmail.com \
--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