From: Andrew Morton <akpm@linux-foundation.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Stanislaw Gruszka <sgruszka@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 4/4] selftests: Add basic posix timers selftests
Date: Mon, 18 Mar 2013 14:26:23 -0700 [thread overview]
Message-ID: <20130318142623.a6a9dd7be1ca9dcd1cd0caec@linux-foundation.org> (raw)
In-Reply-To: <1363366442-11494-5-git-send-email-fweisbec@gmail.com>
On Fri, 15 Mar 2013 17:54:02 +0100 Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Add some initial basic tests on a few posix timers
> interface such as setitimer() and timer_settime().
>
> These simply check that expiration happens in a reasonable
> timeframe after expected elapsed clock time (user time,
> user + system time, real time, ...).
>
> This is helpful for finding basic breakages while hacking
> on this subsystem.
>
> ...
>
> tools/testing/selftests/timers/Makefile | 8 +
I wonder if this should be tools/testing/posix-timers/, to leave room
in the namespace for other varieties of timer.
next prev parent reply other threads:[~2013-03-18 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 16:53 [PATCH 0/4] posix_cpu_timers: Some code consolidation v2 Frederic Weisbecker
2013-03-15 16:53 ` [PATCH 1/4] posix_cpu_timer: Consolidate expiry time type Frederic Weisbecker
2013-03-19 22:43 ` Andrew Morton
2013-03-20 0:25 ` Frederic Weisbecker
2013-03-15 16:54 ` [PATCH 2/4] posix_cpu_timers: Consolidate timer list cleanups Frederic Weisbecker
2013-03-15 16:54 ` [PATCH 3/4] posix_cpu_timers: Consolidate expired timers check Frederic Weisbecker
2013-03-15 16:54 ` [PATCH 4/4] selftests: Add basic posix timers selftests Frederic Weisbecker
2013-03-18 21:26 ` Andrew Morton [this message]
2013-03-18 21:32 ` Frederic Weisbecker
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=20130318142623.a6a9dd7be1ca9dcd1cd0caec@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sgruszka@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®