* [PATCH] timer_getoverrun.2:tfix
@ 2014-04-20 4:41 Yuri Kozlov
[not found] ` <1397968868-4466-1-git-send-email-yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org>
0 siblings, 1 reply; 2+ messages in thread
From: Yuri Kozlov @ 2014-04-20 4:41 UTC (permalink / raw)
To: Michael Kerrisk; +Cc: linux-man-u79uwXL29TY76Z2rM5mHXA, Yuri Kozlov
---
man2/timer_getoverrun.2 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man2/timer_getoverrun.2 b/man2/timer_getoverrun.2
index d64255a..c14230b 100644
--- a/man2/timer_getoverrun.2
+++ b/man2/timer_getoverrun.2
@@ -78,7 +78,7 @@ Timer overruns can also occur when expiration notifications
are delivered via invocation of a thread,
since there may be an arbitrary delay between an expiration of the timer
and the invocation of the notification thread,
-and in that delay interval, additional timer expirations may occur
+and in that delay interval, additional timer expirations may occur.
.SH RETURN VALUE
On success,
.BR timer_getoverrun ()
--
1.9.1
--
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] timer_getoverrun.2:tfix
[not found] ` <1397968868-4466-1-git-send-email-yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org>
@ 2014-04-20 8:43 ` Michael Kerrisk (man-pages)
0 siblings, 0 replies; 2+ messages in thread
From: Michael Kerrisk (man-pages) @ 2014-04-20 8:43 UTC (permalink / raw)
To: Yuri Kozlov
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w,
linux-man-u79uwXL29TY76Z2rM5mHXA
Thanks, Yuri. Applied.
Cheers,
Michael
On 04/20/2014 06:41 AM, Yuri Kozlov wrote:
> ---
> man2/timer_getoverrun.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/timer_getoverrun.2 b/man2/timer_getoverrun.2
> index d64255a..c14230b 100644
> --- a/man2/timer_getoverrun.2
> +++ b/man2/timer_getoverrun.2
> @@ -78,7 +78,7 @@ Timer overruns can also occur when expiration notifications
> are delivered via invocation of a thread,
> since there may be an arbitrary delay between an expiration of the timer
> and the invocation of the notification thread,
> -and in that delay interval, additional timer expirations may occur
> +and in that delay interval, additional timer expirations may occur.
> .SH RETURN VALUE
> On success,
> .BR timer_getoverrun ()
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-04-20 8:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-20 4:41 [PATCH] timer_getoverrun.2:tfix Yuri Kozlov
[not found] ` <1397968868-4466-1-git-send-email-yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org>
2014-04-20 8:43 ` Michael Kerrisk (man-pages)
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).