From: Steven Rostedt <rostedt@goodmis.org>
To: Greg KH <gregkh@suse.de>
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, autotest@test.kernel.org,
Vivek Goyal <vgoyal@redhat.com>,
Clark Williams <williams@redhat.com>,
Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [ANNOUNCE] ktest.pl: Easy and flexible testing script for Linux Kernel Developers
Date: Thu, 28 Oct 2010 23:56:59 -0400 [thread overview]
Message-ID: <1288324619.18238.414.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20101029034142.GA12125@suse.de>
On Thu, 2010-10-28 at 20:41 -0700, Greg KH wrote:
> >
> > Should I try to get this into 2.6.37? Since it is a stand alone tool, I
> > can hardly expect that it would break anything else.
>
> I don't see why not, but perhaps you might want to wait for people to
> test it a bit? Then get it into .38?
That's sorta the catch-22. We want testers before pushing it into
mainline, but if it is in mainline we get more testers :-)
I'm not sure it makes a difference now if it goes in or if it does not.
Because it would reside in tools as a helper program, and will not
affect the quality of the kernel whether it's in the kernel tree or not.
Although, I could argue that it may help the quality of the kernel if it
is in the kernel tree because it may have more people testing the
kernel.
One thing I worry about adding it to the tools directory. I could
imagine someone running the tool from the tools directly from the build
source that they are testing. If they do a bisect, a bisect may remove
the tools directory while its running. That would be an interesting
test ;-)
-- Steve
prev parent reply other threads:[~2010-10-29 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 19:42 Steven Rostedt
2010-10-29 0:27 ` Greg KH
2010-10-29 3:10 ` Steven Rostedt
2010-10-29 3:41 ` Greg KH
2010-10-29 3:56 ` 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=1288324619.18238.414.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=acme@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=autotest@test.kernel.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=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
all inboxes | Powered by JetHome®