From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Andrew Hunter <andrewhhunter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: typo in man pthread_sigqueue
Date: Fri, 13 Sep 2013 05:49:18 +0200 [thread overview]
Message-ID: <52328B3E.9090800@gmail.com> (raw)
In-Reply-To: <CANf_6TjALmwh=oLA99aTvNeabX6knei8dQvcDYt=LTW_ZtaQkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 12.09.2013 23:40, Andrew Hunter wrote:
> The type of pthread_sigqueue is reported in the manpage (both online
> and in any package I can find) as
>
> int pthread_sigqueue(pthread_t *thread, int sig,
> const union sigval value);
>
> I believe this is incorrect; thread is a pthread_t, not a pthread_t*.
> This can be easily verified by looking at the source:
> http://www.eglibc.org/cgi-bin/viewvc.cgi/trunk/libc/nptl/sysdeps/unix/sysv/linux/pthread_sigqueue.c?view=markup
>
> (Or just by noting that throughout pthreads, pthread_ts are passed by
> value. The only other pthread_t * that comes to mind is the one
> initialized by pthread_create.)
>
> I'd send a patch myself but I'm not clear where the manpages sources
> are and don't have time to go searching right now--my apologies.
Thanks for the report, Andrew. Fixed now.
Cheers,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-09-13 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 21:40 typo in man pthread_sigqueue Andrew Hunter
[not found] ` <CANf_6TjALmwh=oLA99aTvNeabX6knei8dQvcDYt=LTW_ZtaQkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-13 3:49 ` 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=52328B3E.9090800@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=andrewhhunter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.