From: dank@kegel.com
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
george@mvista.com,
"high-res-timers-discourse@lists.sourceforge.net"
<high-res-timers-discourse@lists.sourceforge.net>
Subject: high resolution timers in 2.5? (was: [2.6] The List, pass #2)
Date: Fri, 19 Jul 2002 09:54:03 -0700 [thread overview]
Message-ID: <3D38442B.FC307ADE@kegel.com> (raw)
Mark Salisbury wrote:
> On Friday 19 July 2002 00:47, Guillaume Boissiere wrote:
> > Would be nice to have before feature freeze, but most likely 2.7:
> > o High resolution timers
>
> this has been done for almost a year now, what is holding it up?
I don't know, but it's about time. George Anziger should know.
George,
Have you submitted a high-resolution-timers patch to Linux for 2.5?
I seem to recall he didn't like the patch when he first saw
it, but that was so long ago presumably it's much cleaner now?
- Dan
next reply other threads:[~2002-07-19 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 16:54 dank [this message]
2002-07-19 20:26 ` high resolution timers in 2.5? (was: [2.6] The List, pass #2) george anzinger
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=3D38442B.FC307ADE@kegel.com \
--to=dank@kegel.com \
--cc=george@mvista.com \
--cc=high-res-timers-discourse@lists.sourceforge.net \
--cc=linux-kernel@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
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