From: Satoru Takeuchi <satoru.takeuchi@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>
Subject: [RFC] ktest doc: Automated test of linux kernel by using ktest v1.1.3
Date: Sun, 28 Sep 2014 09:21:10 +0900 [thread overview]
Message-ID: <87d2agsih5.wl%satoru.takeuchi@gmail.com> (raw)
Hi,
I revised ktest documentation.
v1.1.2->v1.1.3: Support not only debian/jessy, but also CentOS7 as target system
http://www.slideshare.net/satorutakeuchi18/kernel-auto-testbyktest
It's not the ktest reference guild, but the quick learning guild of ktest
especially focuses on some important features.
After reading this document, you'll be able to do the following work automatically.
- test all patches of your patchset, and
- bisect to find the problematic commit
I believe it saves plenty of your time.
Feel free to ask me if you have any comments/questions.
Thanks,
Satoru
reply other threads:[~2014-09-28 0:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87d2agsih5.wl%satoru.takeuchi@gmail.com \
--to=satoru.takeuchi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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