From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/9] ktest: queue for 2.6.39
Date: Tue, 08 Mar 2011 10:21:58 -0500 [thread overview]
Message-ID: <20110308152158.799699072@goodmis.org> (raw)
I'm publishing these just to let people know what I plan on pushing
out come 2.6.39 merge window.
Steven Rostedt (9):
ktest: Print logfile name on failure
ktest: Start failure timeout on panic too
ktest: Handle kernels before make oldnoconfig
ktest: Add manual bisect
ktest: Add BISECT_SKIP
ktest: Add BISECT_FILES to run git bisect on paths
ktest: Fix bug where the test would not end after failure
ktest: Monitor kernel while running of user tests
ktest: Add STOP_TEST_AFTER to stop the test after a period of time
----
tools/testing/ktest/ktest.pl | 139 +++++++++++++++++++++++++++++++++------
tools/testing/ktest/sample.conf | 42 ++++++++++++
2 files changed, 161 insertions(+), 20 deletions(-)
next reply other threads:[~2011-03-08 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 15:21 Steven Rostedt [this message]
2011-03-08 15:21 ` [PATCH 1/9] ktest: Print logfile name on failure Steven Rostedt
2011-03-08 15:22 ` [PATCH 2/9] ktest: Start failure timeout on panic too Steven Rostedt
2011-03-08 15:22 ` [PATCH 3/9] ktest: Handle kernels before make oldnoconfig Steven Rostedt
2011-03-08 15:22 ` [PATCH 4/9] ktest: Add manual bisect Steven Rostedt
2011-03-08 15:22 ` [PATCH 5/9] ktest: Add BISECT_SKIP Steven Rostedt
2011-03-08 15:22 ` [PATCH 6/9] ktest: Add BISECT_FILES to run git bisect on paths Steven Rostedt
2011-03-08 15:22 ` [PATCH 7/9] ktest: Fix bug where the test would not end after failure Steven Rostedt
2011-03-08 15:22 ` [PATCH 8/9] ktest: Monitor kernel while running of user tests Steven Rostedt
2011-03-08 15:22 ` [PATCH 9/9] ktest: Add STOP_TEST_AFTER to stop the test after a period of time Steven Rostedt
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=20110308152158.799699072@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--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