From: Joe Korty <joe.korty@ccur.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Daniel Walker <dwalker@mvista.com>,
"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
akpm@osdl.org, george@mvista.com, johnstul@us.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: FW: [RFC] A more general timeout specification
Date: Thu, 1 Sep 2005 09:53:11 -0400 [thread overview]
Message-ID: <20050901135311.GC1753@tsunami.ccur.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0509011119580.3728@scrub.home>
On Thu, Sep 01, 2005 at 11:22:32AM +0200, Roman Zippel wrote:
> For a timeout? Please get real.
> If you need more precision, use a dedicated timer API, but don't make the
> general case more complex for the 99.99% of other users.
Struct timeout is just a struct timespec + a bit for absolute/relative +
a field for clock specification. What's so complex about that? It captures
everything needed to specify time, from here to the end of time.
Joe
next prev parent reply other threads:[~2005-09-01 13:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 23:24 FW: [RFC] A more general timeout specification Perez-Gonzalez, Inaky
2005-08-31 23:50 ` Roman Zippel
2005-09-01 0:08 ` Daniel Walker
2005-09-01 9:22 ` Roman Zippel
2005-09-01 13:53 ` Joe Korty [this message]
2005-09-01 13:50 ` Joe Korty
2005-09-01 14:32 ` Roman Zippel
2005-09-01 15:10 ` Daniel Walker
2005-09-01 15:11 ` Daniel Walker
2005-09-01 15:47 ` Joe Korty
-- strict thread matches above, loose matches on Subject: below --
2005-09-01 11:59 Perez-Gonzalez, Inaky
2005-09-01 12:55 ` Roman Zippel
2005-09-01 0:00 Perez-Gonzalez, Inaky
2005-09-01 9:19 ` Roman Zippel
2005-09-01 13:48 ` Joe Korty
2005-09-01 15:18 ` Roman Zippel
2005-08-31 23:17 Perez-Gonzalez, Inaky
2005-08-31 22:15 Perez-Gonzalez, Inaky
2005-08-31 23:01 ` Roman Zippel
2005-08-31 22:11 Perez-Gonzalez, Inaky
2005-08-31 23:06 ` Christopher Friesen
2005-08-31 20:55 Perez-Gonzalez, Inaky
2005-08-31 21:15 ` Joe Korty
2005-08-31 21:20 ` Christopher Friesen
2005-08-31 21:34 ` Joe Korty
2005-08-31 22:06 ` Christopher Friesen
2005-08-31 22:10 ` Roman Zippel
2005-08-23 1:13 Perez-Gonzalez, Inaky
2005-05-18 20:15 Joe Korty
2005-07-29 1:52 ` FW: " Inaky Perez-Gonzalez
2005-08-22 22:56 ` john stultz
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=20050901135311.GC1753@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=akpm@osdl.org \
--cc=dwalker@mvista.com \
--cc=george@mvista.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.