Linux-man Archive on lore.kernel.org
 help / color / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Benjamin Peterson <benjamin@python.org>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] clock_getres.2: Document CLOCK_TAI
Date: Thu, 26 Mar 2020 08:48:07 +0100
Message-ID: <de3c5180-9bd9-a0c6-849d-37538990184d@gmail.com> (raw)
In-Reply-To: <20200321220809.3430-1-benjamin@python.org>

Hello Benjamin,

Thanks! Patch applied. (Just for the future, when you send a second
version of a patch, it make life a little easier for me if you note
what has changed.)

Cheers,

Michael


On 3/21/20 11:08 PM, Benjamin Peterson wrote:
> Signed-off-by: Benjamin Peterson <benjamin@python.org>
> ---
>  man2/clock_getres.2 | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/man2/clock_getres.2 b/man2/clock_getres.2
> index 3fb0ac61c..7b25b8f65 100644
> --- a/man2/clock_getres.2
> +++ b/man2/clock_getres.2
> @@ -137,6 +137,16 @@ Requires per-architecture support,
>  and probably also architecture support for this flag in the
>  .BR vdso (7).
>  .TP
> +.BR CLOCK_TAI " (since Linux 3.10; Linux-specific)"
> +.\" Added in commit 1ff3c9677bff7e468e0c487d0ffefe4e901d33f4
> +System-wide clock derived from wall time but ignoring leap seconds. This clock does
> +not experience discontinuities and backwards jumps caused by NTP inserting leap
> +seconds as
> +.BR CLOCK_REALTIME
> +does.
> +.IP
> +The acronym TAI refers to International Atomic Time.
> +.TP
>  .B CLOCK_MONOTONIC
>  Clock that cannot be set and represents monotonic time since\(emas described
>  by POSIX\(em"some unspecified point in the past".
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21  4:03 Benjamin Peterson
2020-03-21 22:08 ` Benjamin Peterson
2020-03-26  7:48   ` 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=de3c5180-9bd9-a0c6-849d-37538990184d@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=benjamin@python.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

Linux-man Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-man/0 linux-man/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-man linux-man/ https://lore.kernel.org/linux-man \
		linux-man@vger.kernel.org
	public-inbox-index linux-man

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-man


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git