From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org, enh <enh@google.com>,
Bruno Haible <bruno@clisp.org>
Cc: Alejandro Colomar <alx@kernel.org>,
Stefan Puiu <stefan.puiu@gmail.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: [PATCH v3 3/3] clock_nanosleep.2: Use 't' rather than 'request'
Date: Tue, 5 Mar 2024 02:26:15 +0100 [thread overview]
Message-ID: <20240305012507.9316-2-alx@kernel.org> (raw)
In-Reply-To: <ZeZxSydsfskaQ5Vw@debian>
[-- Attachment #1: Type: text/plain, Size: 2269 bytes --]
It seems much more clear.
Cc: Elliott Hughes <enh@google.com>
Cc: Stefan Puiu <stefan.puiu@gmail.com>
Cc: Bruno Haible <bruno@clisp.org>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---
v3:
- Add new patch for clock_nanosleep(2).
- Patches 1 and 2 are still the same as in older revisions; not
resending.
man2/clock_nanosleep.2 | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/man2/clock_nanosleep.2 b/man2/clock_nanosleep.2
index 5bda50e18..7715ec385 100644
--- a/man2/clock_nanosleep.2
+++ b/man2/clock_nanosleep.2
@@ -19,7 +19,7 @@ .SH SYNOPSIS
.nf
.P
.BI "int clock_nanosleep(clockid_t " clockid ", int " flags ,
-.BI " const struct timespec *" request ,
+.BI " const struct timespec *" t ,
.BI " struct timespec *_Nullable " remain );
.fi
.P
@@ -94,7 +94,7 @@ .SH DESCRIPTION
If
.I flags
is 0, then the value specified in
-.I request
+.I t
is interpreted as an interval relative to the current
value of the clock specified by
.IR clockid .
@@ -104,11 +104,11 @@ .SH DESCRIPTION
is
.BR TIMER_ABSTIME ,
then
-.I request
+.I t
is interpreted as an absolute time as measured by the clock,
.IR clockid .
If
-.I request
+.I t
is less than or equal to the current value of the clock,
then
.BR clock_nanosleep ()
@@ -117,7 +117,7 @@ .SH DESCRIPTION
.BR clock_nanosleep ()
suspends the execution of the calling thread
until either at least the time specified by
-.I request
+.I t
has elapsed,
or a signal is delivered that causes a signal handler to be called or
that terminates the process.
@@ -146,7 +146,7 @@ .SH RETURN VALUE
.SH ERRORS
.TP
.B EFAULT
-.I request
+.I t
or
.I remain
specified an invalid address.
@@ -180,7 +180,7 @@ .SH HISTORY
glibc 2.1.
.SH NOTES
If the interval specified in
-.I request
+.I t
is not an exact multiple of the granularity underlying clock (see
.BR time (7)),
then the interval will be rounded up to the next multiple.
@@ -216,7 +216,7 @@ .SH NOTES
is
.BR TIMER_ABSTIME .
(An absolute sleep can be restarted using the same
-.I request
+.I t
argument.)
.P
POSIX.1 specifies that
--
2.43.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-05 1:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 20:51 [PATCH] prctl.2: Fix typo Bruno Haible
2023-10-31 12:40 ` Alejandro Colomar
2023-10-31 14:31 ` Stefan Puiu
2023-10-31 16:11 ` Alejandro Colomar
2023-10-31 16:19 ` enh
2023-10-31 18:40 ` Alejandro Colomar
2023-10-31 19:15 ` enh
2023-10-31 21:23 ` Alejandro Colomar
2023-11-01 0:37 ` enh
2023-11-01 10:16 ` Alejandro Colomar
2024-03-03 12:15 ` [PATCH 0/2] Use terms consistently in function parameter names Alejandro Colomar
2024-03-03 12:15 ` [PATCH 1/2] man*/: epoll_*(), fcntl(), flock(), ioctl(), msgctl(), *prctl(), ptrace(), quotactl(), reboot(), semctl(), shmctl(), lockf(): Consistently use 'op' and 'operation' Alejandro Colomar
2024-03-05 18:12 ` Alejandro Colomar
2024-03-05 19:19 ` enh
2024-03-03 12:15 ` [PATCH 2/2] clock_nanosleep.2, nanosleep.2: Use 'duration' rather than 'request' Alejandro Colomar
2024-03-03 12:45 ` Bruno Haible
2024-03-03 12:55 ` Alejandro Colomar
2024-03-03 13:02 ` [PATCH v2 2/2] " Alejandro Colomar
2024-03-05 0:18 ` [PATCH 2/2] clock_nanosleep.2, " enh
2024-03-05 0:34 ` Alejandro Colomar
2024-03-05 0:56 ` enh
2024-03-05 1:11 ` Alejandro Colomar
2024-03-05 1:26 ` Alejandro Colomar [this message]
2024-03-05 22:22 ` enh
2023-10-31 17:08 ` [PATCH] prctl.2: Fix typo Bruno Haible
2023-10-31 21:20 ` 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=20240305012507.9316-2-alx@kernel.org \
--to=alx@kernel.org \
--cc=bruno@clisp.org \
--cc=enh@google.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=stefan.puiu@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