From: Mel Gorman <mgorman@suse.de>
To: Greg KH <greg@kroah.com>, chrubis@suse.cz
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] kernel testing standard
Date: Thu, 5 Jun 2014 07:54:55 +0100 [thread overview]
Message-ID: <20140605065455.GM10819@suse.de> (raw)
In-Reply-To: <20140605002331.GB24037@kroah.com>
On Wed, Jun 04, 2014 at 05:23:31PM -0700, Greg KH wrote:
> On Fri, May 30, 2014 at 02:07:36PM +0200, Linus Walleij wrote:
> > On Wed, May 28, 2014 at 8:57 PM, Greg KH <greg@kroah.com> wrote:
> > > On Wed, May 28, 2014 at 04:37:02PM +0100, Mel Gorman wrote:
> > >> As LTP is reported to
> > >> be sane these days for some tests, it could conceivably be wrapped by "make
> > >> test" to avoid duplicating effort there. I think that would be worthwhile
> > >> if someone had the time to push it because it would be an unconditional win.
> > >
> > > That is what I have been asking for for _years_. Hopefully someday
> > > someone does this...
> >
> > Does this read "let's pull LTP into the kernel source tree"?
>
> Everyone always asks this, and I say, "Sure, why not?"
>
> Actually, if people do complain about "why", then let's take the
> "useful" subset of LTP for kernel developers. It's a great place to
> start, don't you agree?
>
Cyril Hrubis is an LTP expert who has spend a considerable amount of time
cleaning it up but is not often seen in kernel development circles so I added
him to the cc. He's stated before that there is a large subset of LTP that
is considerably cleaner than it was a few years ago. Cyril, you are probably
not subscribed but the list archives for the "kernel testing standard" thread
can be seen at http://lists.linuxfoundation.org/pipermail/ksummit-discuss/
if you dig around a bit.
There is a hazard that someone bisecting the tree would need to be careful
to not bisect LTP instead. Otherwise, in your opinion how feasible
would it be to import the parts of LTP you trust into the kernel tree
under tools/testing/ ?
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2014-06-05 6:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 11:47 Masami Hiramatsu
2014-05-23 13:32 ` Jason Cooper
2014-05-23 16:24 ` Olof Johansson
2014-05-23 16:35 ` Guenter Roeck
2014-05-23 16:36 ` Jason Cooper
2014-05-23 18:10 ` Masami Hiramatsu
2014-05-23 18:36 ` Jason Cooper
2014-05-23 18:06 ` Masami Hiramatsu
2014-05-23 18:32 ` Jason Cooper
2014-05-23 14:05 ` Justin M. Forbes
2014-05-23 16:04 ` Mark Brown
2014-05-24 0:30 ` Theodore Ts'o
2014-05-24 1:15 ` Guenter Roeck
2014-05-26 11:33 ` Masami Hiramatsu
2014-05-30 18:35 ` Steven Rostedt
2014-05-30 20:59 ` Kees Cook
2014-05-30 22:53 ` Theodore Ts'o
2014-06-04 13:51 ` Masami Hiramatsu
2014-05-26 17:08 ` Daniel Vetter
2014-05-26 18:21 ` Mark Brown
2014-05-28 15:37 ` Mel Gorman
2014-05-28 18:57 ` Greg KH
2014-05-30 12:07 ` Linus Walleij
2014-06-05 0:23 ` Greg KH
2014-06-05 6:54 ` Mel Gorman [this message]
2014-06-05 8:30 ` Geert Uytterhoeven
2014-06-05 8:44 ` chrubis
2014-06-05 8:53 ` Daniel Vetter
2014-06-05 11:17 ` Masami Hiramatsu
2014-06-05 11:58 ` Daniel Vetter
2014-06-06 9:10 ` Masami Hiramatsu
2014-06-05 14:10 ` James Bottomley
2014-06-06 9:17 ` Masami Hiramatsu
2014-06-09 14:44 ` chrubis
2014-06-09 17:54 ` Michael Kerrisk (man-pages)
2014-06-05 8:39 ` chrubis
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=20140605065455.GM10819@suse.de \
--to=mgorman@suse.de \
--cc=chrubis@suse.cz \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.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