From: "Michael Kerrisk \(man-pages\) via Libc-alpha" <libc-alpha@sourceware.org>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org,
mtk.manpages@gmail.com
Subject: Re: [PATCH v2 2/3] system_data_types.7: Add 'clock_t'
Date: Sun, 18 Oct 2020 15:10:33 +0200 [thread overview]
Message-ID: <4f9d936f-3bdb-c450-75fd-6ba92396bf05@gmail.com> (raw)
In-Reply-To: <20201018094917.9293-1-colomar.6.4.3@gmail.com>
On 10/18/20 11:49 AM, Alejandro Colomar wrote:
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
Thanks, Alex. Patch applied.
Cheers,
Michael
> ---
> man7/system_data_types.7 | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
> index 8a894b2e0..abc456f0b 100644
> --- a/man7/system_data_types.7
> +++ b/man7/system_data_types.7
> @@ -85,6 +85,31 @@ See also:
> .BR aio_write (3),
> .BR lio_listio (3)
> .RE
> +.\"------------------------------------- clock_t ----------------------/
> +.TP
> +.I clock_t
> +.RS
> +Include:
> +.I <time.h>
> +or
> +.IR <sys/types.h> .
> +Alternatively,
> +.IR <sys/time.h> .
> +.PP
> +Used for system time in clock ticks or
> +.B CLOCKS_PER_SEC
> +(defined in
> +.IR <time.h> ).
> +According to POSIX,
> +it shall be an integer type or a real-floating type.
> +.PP
> +Conforming to:
> +C99 and later; POSIX.1-2001 and later.
> +.PP
> +See also:
> +.BR times (2),
> +.BR clock (3)
> +.RE
> .\"------------------------------------- div_t ------------------------/
> .TP
> .I div_t
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-10-18 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 9:49 [PATCH v2 2/3] system_data_types.7: Add 'clock_t' Alejandro Colomar via Libc-alpha
2020-10-18 13:10 ` Michael Kerrisk (man-pages) via Libc-alpha [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f9d936f-3bdb-c450-75fd-6ba92396bf05@gmail.com \
--to=libc-alpha@sourceware.org \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).