From: george anzinger <george@mvista.com>
To: Andrew Morton <akpm@digeo.com>
Cc: anton@samba.org, davem@redhat.com, torvalds@transmeta.com,
"'high-res-timers-discourse@lists.sourceforge.net'"
<high-res-timers-discourse@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Randy.Dunlap" <rddunlap@osdl.org>
Subject: POSIX clocks and timers tests update
Date: Fri, 21 Feb 2003 01:17:27 -0800 [thread overview]
Message-ID: <3E55EEA7.6060401@mvista.com> (raw)
In-Reply-To: <20030220003902.6156d00e.akpm@digeo.com>
The POSIX clocks and timers support package on sourceforge has been
updated. It now _should_ work with all platforms. I am sure you will
tell me if it doesn't :)
This should make it easy to test new archs as they connect the POSIX
clocks and timers system calls.
I have also included a new timer stress test from Randy Dunlap.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
parent reply other threads:[~2003-02-21 9:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20030220003902.6156d00e.akpm@digeo.com>]
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=3E55EEA7.6060401@mvista.com \
--to=george@mvista.com \
--cc=akpm@digeo.com \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=high-res-timers-discourse@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=torvalds@transmeta.com \
/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