From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/4] [GIT PULL] ktest: Updates for 3.18
Date: Tue, 07 Oct 2014 17:16:31 -0400 [thread overview]
Message-ID: <20141007211631.365194240@goodmis.org> (raw)
Linus,
A fix and a clean up to ktest, as well as two small features.
A way to allow users to skip a manual bisect.
Allowing cherry picked patches to be tested.
The cherry pick worked for a test I needed, but stressing it may
not have all the desired effects. It doesn't cause any regressions
so I kept it in.
Please pull the latest ktest-v3.18 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
ktest-v3.18
Tag SHA1: 48c20121c5971c194410fa229d5797811a25a9e8
Head SHA1: d832d743385dd5e735660951aa9d7d36a6a4176a
Chris J Arges (1):
ktest: add ability to skip during BISECT_MANUAL
Steven Rostedt (Red Hat) (3):
ktest: Add PATCHCHECK_CHERRY
ktest: Fix check for new kernel success on rebooting to good kernel
ktest: Don't bother with bisect good or bad on replay
----
tools/testing/ktest/ktest.pl | 61 +++++++++++++++++++++++++++++++----------
tools/testing/ktest/sample.conf | 10 +++++++
2 files changed, 57 insertions(+), 14 deletions(-)
next reply other threads:[~2014-10-07 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 21:16 Steven Rostedt [this message]
2014-10-07 21:16 ` [PATCH 1/4] ktest: Add PATCHCHECK_CHERRY Steven Rostedt
2014-10-07 21:16 ` [PATCH 2/4] ktest: add ability to skip during BISECT_MANUAL Steven Rostedt
2014-10-07 21:16 ` [PATCH 3/4] ktest: Fix check for new kernel success on rebooting to good kernel Steven Rostedt
2014-10-07 21:16 ` [PATCH 4/4] ktest: Dont bother with bisect good or bad on replay 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=20141007211631.365194240@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.