From: Steven Rostedt <rostedt@goodmis.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Jon Masters <jcm@redhat.com>, corbet <corbet@lwn.net>,
Jake Edge <jake@lwn.net>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
lmr@redhat.com, Greg Kroah-Hartman <gregkh@suse.de>,
Clark Williams <williams@redhat.com>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: [ANNOUNCE v2] ktest.pl: Easy and flexible testing script for Linux Kernel Developers (now with config bisect)
Date: Thu, 18 Nov 2010 09:38:03 -0500 [thread overview]
Message-ID: <1290091083.30543.125.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20101118142623.GB13933@redhat.com>
[ Finally remembered to remove that annoying autotest@test.kernel.org
from the Cc list ]
On Thu, 2010-11-18 at 09:26 -0500, Vivek Goyal wrote:
> On Thu, Nov 18, 2010 at 09:08:37AM -0500, Steven Rostedt wrote:
> > Question:
> >
> > Has anyone tried this out? Does anyone feel that I should get this ready
> > to be included in 2.6.38 tools directory?
> >
> > Just want to know if I should go ahead and prepare it, or if it will
> > just be a waste of my time.
>
> I had done some testing only on initial internal version but did not
> get a chance to do more testing later.
>
> But I believe it is worth to put effort to keep this script going. I am
> especially interested in part where I can just automate compilation and
> testing of a patch on a remote machine.
Thanks for the reply! I'll start setting up a git tree that places all
the changes into the tools directory.
-- Steve
prev parent reply other threads:[~2010-11-18 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 23:45 [ANNOUNCE v2] ktest.pl: Easy and flexible testing script for Linux Kernel Developers (now with config bisect) Steven Rostedt
2010-11-18 7:03 ` Jon Masters
2010-11-18 11:49 ` Steven Rostedt
2010-11-18 14:08 ` Steven Rostedt
2010-11-18 14:26 ` Vivek Goyal
2010-11-18 14:38 ` Steven Rostedt [this message]
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=1290091083.30543.125.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=acme@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@suse.de \
--cc=jake@lwn.net \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mchehab@infradead.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.com \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@redhat.com \
--cc=williams@redhat.com \
/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