From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: [BUG] sigaction.2: s/sigval_t/union sigval/
Date: Wed, 16 Sep 2020 15:14:42 +0200 [thread overview]
Message-ID: <181e9d30-baf7-cc5c-3016-71e83504ab04@gmail.com> (raw)
Hi Michael,
sigaction.2 uses the name 'sigval_t', which is:
// <x86_64-linux-gnu/bits/types/__sigval_t.h>
/* Type for data associated with a signal. */
#ifdef __USE_POSIX199309
union sigval
{
int sival_int;
void *sival_ptr;
};
typedef union sigval __sigval_t;
#else
union __sigval
{
int __sival_int;
void *__sival_ptr;
};
typedef union __sigval __sigval_t;
#endif
and then:
x86_64-linux-gnu/bits/types/sigval_t.h:16:typedef __sigval_t sigval_t;
I think the man page should use the POSIX naming, shouldn't it?
___________
BTW: I sent Draft v6 for system_data_types.7 2h+ ago, but I don't see
it on lore.kernel.org.
Did you receive it? Should I wait, or send it again?
Thanks,
Alex
next reply other threads:[~2020-09-16 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 13:14 Alejandro Colomar [this message]
2020-09-16 14:29 ` [BUG] sigaction.2: s/sigval_t/union sigval/ 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=181e9d30-baf7-cc5c-3016-71e83504ab04@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