From: "Network Nut" <sillystack-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: FW: WaitForMultipleObjects/etc. In Kernel
Date: Mon, 27 Jan 2014 15:21:08 -0600 [thread overview]
Message-ID: <00f001cf1ba5$b22f45b0$168dd110$@gmail.com> (raw)
In-Reply-To: <52E6219A.3020405-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
See below.
-----Original Message-----
From: Clemens Ladisch [mailto:clemens-P6GI/4k7KOmELgA04lAiVw@public.gmane.org]
Sent: Monday, January 27, 2014 3:07 AM
To: Network Nut
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: WaitForMultipleObjects/etc. In Kernel
> BTW, the man page for epoll_wait seems to be incorrect.
<https://www.kernel.org/doc/man-pages/reporting_bugs.html>
> "The timeout argument specifies the minimum number of milliseconds
> that epoll_wait() will block."
>
> I think the word "minimum" should be "maximum".
-Nut
--
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
next parent reply other threads:[~2014-01-27 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00d901cf1a19$0ea62db0$2bf28910$@gmail.com>
[not found] ` <52E554EC.3090900@ladisch.de>
[not found] ` <012d01cf1ae3$6543e340$2fcba9c0$@gmail.com>
[not found] ` <52E6219A.3020405@ladisch.de>
[not found] ` <52E6219A.3020405-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
2014-01-27 21:21 ` Network Nut [this message]
2014-01-29 10:40 ` FW: WaitForMultipleObjects/etc. In Kernel Michael Kerrisk (man-pages)
[not found] ` <52E8DA80.7080204-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-30 20:04 ` Network Nut
2014-01-31 6:56 ` Michael Kerrisk (man-pages)
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='00f001cf1ba5$b22f45b0$168dd110$@gmail.com' \
--to=sillystack-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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).