From: Greg KH <greg@kroah.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] [nomination] Move Fast and Oops Things
Date: Wed, 21 May 2014 16:55:47 +0900 [thread overview]
Message-ID: <20140521075547.GA20121@kroah.com> (raw)
In-Reply-To: <CAPcyv4ivq-03wGAarZFxJZa2wXD2zja251v6YQD86BaHvu6h4w@mail.gmail.com>
On Wed, May 21, 2014 at 12:48:48AM -0700, Dan Williams wrote:
> With regards to saying "no" faster, it seems kernel code rarely comes
> with tests. However, maintainers today are already able to reduce the
> latency to "no" when the 0-day-kbuild robot emits a negative test.
> Why not arm that system with tests it can autodiscover? What has held
> back unit test culture in the kernel?
The fact that no one has stepped up and taken maintainership of the
tests and ensure that they continue to work.
I'm working on solving that issue, by getting funding for someone to do
this and focus on tests that all developers and maintainers can use to
help ensure that nothing broke when they make a change. Give me a few
months, hopefully there will be something I can talk about soon in this
area.
thanks,
greg k-h
next prev parent reply other threads:[~2014-05-21 7:56 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 23:13 Dan Williams
2014-05-16 2:56 ` NeilBrown
2014-05-16 15:04 ` Chris Mason
2014-05-16 17:09 ` Andy Grover
2014-05-23 8:11 ` Dan Carpenter
2014-05-16 18:31 ` Randy Dunlap
2014-05-21 7:48 ` Dan Williams
2014-05-21 7:55 ` Greg KH [this message]
2014-05-21 9:05 ` Matt Fleming
2014-05-21 12:52 ` Greg KH
2014-05-21 13:23 ` Matt Fleming
2014-05-21 8:25 ` NeilBrown
2014-05-21 8:36 ` Dan Williams
2014-05-21 8:53 ` Matt Fleming
2014-05-21 10:11 ` NeilBrown
2014-05-21 15:35 ` Dan Williams
2014-05-21 23:06 ` Rafael J. Wysocki
2014-05-21 23:03 ` Dan Williams
2014-05-21 23:40 ` Laurent Pinchart
2014-05-22 0:10 ` Rafael J. Wysocki
2014-05-22 15:48 ` Theodore Ts'o
2014-05-22 16:31 ` Dan Williams
2014-05-22 17:38 ` Theodore Ts'o
2014-05-22 18:42 ` Dan Williams
2014-05-22 19:06 ` Chris Mason
2014-05-22 20:31 ` Dan Carpenter
2014-05-22 20:56 ` Geert Uytterhoeven
2014-05-23 6:21 ` James Bottomley
2014-05-23 14:11 ` John W. Linville
2014-05-24 9:14 ` James Bottomley
2014-05-24 19:19 ` Geert Uytterhoeven
2014-05-23 2:13 ` Greg KH
2014-05-23 3:03 ` Dan Williams
2014-05-23 7:44 ` Greg KH
2014-05-23 14:02 ` Josh Boyer
2014-05-21 23:48 ` NeilBrown
2014-05-22 4:04 ` Dan Williams
2014-05-21 7:22 ` Dan Williams
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=20140521075547.GA20121@kroah.com \
--to=greg@kroah.com \
--cc=dan.j.williams@intel.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