From: Christoph Erhardt <fedora@sicherha.de>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: [PATCH] man/man3/pthread_cond_init.3: Fix name of mutex unlock function
Date: Sun, 22 Mar 2026 12:09:09 +0100 [thread overview]
Message-ID: <7245006.9J7NaK4W3v@framework> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 156 bytes --]
Dear maintainers,
please find attached a small patch for the `pthread_cond_init.3` man page that
fixes a typo in a function name.
Best regards,
Christoph
[-- Attachment #1.2: 0001-man-man3-pthread_cond_init.3-Fix-name-of-mutex-unloc.patch --]
[-- Type: text/x-patch, Size: 910 bytes --]
From b3d0b98ff055fb8bf2482430582ef1344e5b34dc Mon Sep 17 00:00:00 2001
From: Christoph Erhardt <fedora@sicherha.de>
Date: Wed, 18 Mar 2026 10:37:39 +0100
Subject: [PATCH] man/man3/pthread_cond_init.3: Fix name of mutex unlock
function
The typo has existed since this man page was introduced with commit
31b1e42d557400b04c92701d8a37b518fb429462.
Signed-off-by: Christoph Erhardt <fedora@sicherha.de>
---
man/man3/pthread_cond_init.3 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/man3/pthread_cond_init.3 b/man/man3/pthread_cond_init.3
index 88600b3a5..3aac94c3d 100644
--- a/man/man3/pthread_cond_init.3
+++ b/man/man3/pthread_cond_init.3
@@ -91,7 +91,7 @@ Nothing happens if no threads are waiting on
atomically unlocks the
.I mutex
(as per
-.BR pthread_unlock_mutex ())
+.BR pthread_mutex_unlock ())
and waits for the condition variable
.I cond
to be signaled.
--
2.53.0
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2026-03-22 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 11:09 Christoph Erhardt [this message]
2026-03-22 22:10 ` [PATCH] man/man3/pthread_cond_init.3: Fix name of mutex unlock function Alejandro Colomar
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=7245006.9J7NaK4W3v@framework \
--to=fedora@sicherha.de \
--cc=alx@kernel.org \
--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