From: "Geoffrey Thomas" <geofft@ldpreload.com>
To: libc-help@sourceware.org
Subject: tiny glibc manual bug
Date: Fri, 08 Sep 2023 20:01:37 -0400 [thread overview]
Message-ID: <d3aa1827-191f-4441-92b2-b681697bc16d@app.fastmail.com> (raw)
I don't have a sourceware bugzilla account, but hopefully this is small enough someone can fix it directly. :) If not I can go get an account.
In manual/threads.texi section "Functions for Waiting According to a Specific Clock" (i.e. https://www.gnu.org/software/libc/manual/html_node/Waiting-with-Explicit-Clocks.html), there's a few functions documented as taking a first parameter pthread_t *thread. It should not be a pointer, just pthread_t thread.
Thanks,
--
Geoffrey Thomas
geofft@ldpreload.com
next reply other threads:[~2023-09-09 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 0:01 Geoffrey Thomas [this message]
2023-10-15 8:12 ` Mike Frysinger
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=d3aa1827-191f-4441-92b2-b681697bc16d@app.fastmail.com \
--to=geofft@ldpreload.com \
--cc=libc-help@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).