From: Greg KH <greg@kroah.com>
To: Mel Gorman <mgorman@suse.de>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] kernel testing standard
Date: Wed, 28 May 2014 11:57:48 -0700 [thread overview]
Message-ID: <20140528185748.GA30673@kroah.com> (raw)
In-Reply-To: <20140528153702.GU23991@suse.de>
On Wed, May 28, 2014 at 04:37:02PM +0100, Mel Gorman wrote:
> make test will be fine for feature verification and some functional
> verification that does not depend on hardware. So new APIs should have test
> cases that demonstrate the feature works and make test would be great for
> that which is something that is not enforced today. 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...
> However, beware of attempting to put all testing under its banner as
> performance testing is never going to fully fit under its umbrella.
No one is saying this is going to be true, but at the least, we want a
way to document _how_ one can run the performance tests if you want to.
thanks,
greg k-h
next prev parent reply other threads:[~2014-05-28 18:54 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 [this message]
2014-05-30 12:07 ` Linus Walleij
2014-06-05 0:23 ` Greg KH
2014-06-05 6:54 ` Mel Gorman
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=20140528185748.GA30673@kroah.com \
--to=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mgorman@suse.de \
/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