From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
Brian Norris <computersforpeace@gmail.com>,
Kees Cook <keescook@chromium.org>,
Fengguang Wu <fengguang.wu@intel.com>,
shuah@kernel.org, LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, linux-kselftest@vger.kernel.org,
yi1.li@linux.intel.com, takahiro.akashi@linaro.org,
Martin Fuzzey <mfuzzey@parkeon.com>,
Alan Cox <alan@linux.intel.com>
Subject: Re: LTS testing with latest kselftests - some failures
Date: Sat, 17 Jun 2017 06:16:35 +0200 [thread overview]
Message-ID: <20170617041635.GA26923@kroah.com> (raw)
In-Reply-To: <20170616194721.GE21846@wotan.suse.de>
On Fri, Jun 16, 2017 at 09:47:21PM +0200, Luis R. Rodriguez wrote:
> Some of the knobs however are for extending tests for
> existing APIs in older kernels, the async and custom fallback one are an
> example. There are a series of test cases later added which could help
> test LTS kernels. Would Linaro pick these test driver enhancements to help
> increase coverage of tests? Or is it not worth it? If its worth it then
> what I was curious was how to help make this easier for this process to
> bloom.
I don't understand, what do you mean by "pick these test driver
enhancements"? What kind of "knobs" are there in tests? Shouldn't the
tests "just work" with no kind of special configuration of the tests be
needed? No user is going to know to enable something special.
Make the tests "just work" please, because given the large number of
them, no one is going to know to look for special things.
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-17 4:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 17:56 LTS testing with latest kselftests - some failures Sumit Semwal
2017-06-15 18:30 ` Shuah Khan
2017-06-15 23:05 ` Alexander Alemayhu
2017-06-15 23:05 ` Alexander Alemayhu
2017-06-16 4:31 ` Sumit Semwal
2017-06-16 7:14 ` Alexander Alemayhu
2017-06-16 7:14 ` Alexander Alemayhu
2017-06-16 7:38 ` Sumit Semwal
2017-06-16 19:26 ` Alexander Alemayhu
2017-06-16 19:26 ` Alexander Alemayhu
2017-06-16 16:46 ` Luis R. Rodriguez
2017-06-16 19:29 ` Greg Kroah-Hartman
2017-06-16 19:47 ` Luis R. Rodriguez
2017-06-17 4:16 ` Greg Kroah-Hartman [this message]
2017-06-19 14:48 ` Luis R. Rodriguez
2017-06-19 14:55 ` Greg Kroah-Hartman
2017-06-19 17:32 ` Luis R. Rodriguez
2017-06-16 23:55 ` Fengguang Wu
2017-06-19 18:56 ` Kees Cook
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=20170617041635.GA26923@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=computersforpeace@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mfuzzey@parkeon.com \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=takahiro.akashi@linaro.org \
--cc=yi1.li@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.