From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755787AbaCOHW6 (ORCPT ); Sat, 15 Mar 2014 03:22:58 -0400 Received: from mail-pa0-f47.google.com ([209.85.220.47]:37354 "EHLO mail-pa0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751044AbaCOHW5 (ORCPT ); Sat, 15 Mar 2014 03:22:57 -0400 Date: Sat, 15 Mar 2014 16:22:49 +0900 Message-ID: <87ha70lyd2.wl%satoru.takeuchi@gmail.com> From: Satoru Takeuchi To: linux-kernel@vger.kernel.org Cc: Steven Rostedt Subject: [RFC] ktest doc: Automated test of linux kernel by using ktest User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/23.4 Mule/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I wrote a ktest document and published it. 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