linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] clock_getres.2: tfix
Date: Tue, 8 May 2012 09:20:38 +1200	[thread overview]
Message-ID: <CAKgNAki72VuX5TPhQTC3WrTuL62usFSGO7CoSO3cPTVS2LO9Jw@mail.gmail.com> (raw)
In-Reply-To: <1336419296-4823-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>

On Tue, May 8, 2012 at 7:34 AM, David Prévot <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org> wrote:
> Introduced in 63f0f3d and 22594a3.

Applied!

Thanks David.

Cheers,

Michael


> ---
>  man2/clock_getres.2 |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/man2/clock_getres.2 b/man2/clock_getres.2
> index 40c44a2..a1e27ad 100644
> --- a/man2/clock_getres.2
> +++ b/man2/clock_getres.2
> @@ -127,7 +127,7 @@ Setting this clock requires appropriate privileges.
>  This clock is affected by discontinuous jumps in the system time
>  (e.g., if the system administrator manually changes the clock),
>  and by the incremental adjustments performed by
> -.BR adjtime (2)
> +.BR adjtime (3)
>  and NTP.
>  .TP
>  .B CLOCK_MONOTONIC
> @@ -136,7 +136,7 @@ some unspecified starting point.
>  This clock is not affected by discontinuous jumps in the system time
>  (e.g., if the system administrator manually changes the clock),
>  but is affected by the incremental adjustments performed by
> -.BR adjtime (2)
> +.BR adjtime (3)
>  and NTP.
>  .TP
>  .BR CLOCK_MONOTONIC_RAW " (since Linux 2.6.28; Linux-specific)"
> @@ -146,7 +146,7 @@ Similar to
>  but provides access to a raw hardware-based time
>  that is not subject to NTP adjustments or
>  the incremental adjustments performed by
> -.BR adjtime (2).
> +.BR adjtime (3).
>  .TP
>  .B CLOCK_PROCESS_CPUTIME_ID
>  High-resolution per-process timer from the CPU.
> @@ -239,7 +239,7 @@ On Linux, these clocks are not settable
>  .\" See http://bugzilla.kernel.org/show_bug.cgi?id=11972
>  .SH "SEE ALSO"
>  .BR date (1),
> -.BR adjtime (2),
> +.BR adjtime (3),
>  .BR gettimeofday (2),
>  .BR settimeofday (2),
>  .BR time (2),
> --
> 1.7.10
>



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-05-07 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 19:34 [PATCH] clock_getres.2: tfix David Prévot
     [not found] ` <1336419296-4823-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-05-07 21:20   ` Michael Kerrisk (man-pages) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-27  4:17 Benjamin Peterson
2020-03-29  7:21 ` Michael Kerrisk (man-pages)
2023-03-31 18:53 Jakub Wilk
2023-03-31 19:50 ` 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=CAKgNAki72VuX5TPhQTC3WrTuL62usFSGO7CoSO3cPTVS2LO9Jw@mail.gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.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 NNTP newsgroup(s).