From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tom Gall <tom.gall@linaro.org>
Cc: linux-kernel@vger.kernel.org,
linux- stable <stable@vger.kernel.org>,
torvalds@linux-foundation.org, shuahkh@osg.samsung.com,
ltp@lists.linux.it, linux-kselftest@vger.kernel.org
Subject: Re: Towards 4.14 LTS
Date: Sun, 19 Nov 2017 08:09:46 -0800 [thread overview]
Message-ID: <7a73bb41-8372-57d3-2aca-6840ca231167@roeck-us.net> (raw)
In-Reply-To: <20171119112051.GA10015@kroah.com>
On 11/19/2017 03:20 AM, Greg Kroah-Hartman wrote:
> On Thu, Nov 16, 2017 at 10:50:23PM -0600, Tom Gall wrote:
>> At Linaro we’ve been putting effort into regularly running kernel tests over
>> arm, arm64 and x86_64 targets. On those targets we’re running mainline, -next,
>> 4.4, and 4.9 kernels and yes we are adding to this list as the hardware
>> capacity grows.
>>
>> For test buckets we’re using just LTP, kselftest and libhugetlbfs and
>> like kernels we will add to this list.
>
> I'm sorry, I don't understand this sentance.
>
My parsing of it is that they will add to the list of tests as well as
to the list of supported kernel versions (and/or maybe architectures ?).
Guenter
>> With the 4.14 cycle being a little ‘different’ in so much as the goal to
>> have it be an LTS kernel I think it’s important to take a look at some
>> 4.14 test results.
>>
>> Grab a beverage, this is a bit of a long post. But quick summery 4.14 as
>> released looks just as good as 4.13, for the test buckets I named above.
>
> Thanks for doing this testing and letting us know.
>
> greg k-h
>
next prev parent reply other threads:[~2017-11-19 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 4:50 Tom Gall
2017-11-19 11:20 ` Greg Kroah-Hartman
2017-11-19 16:09 ` Guenter Roeck [this message]
2017-11-20 16:23 ` Tom Gall
2017-11-21 12:41 ` [LTP] " Cyril Hrubis
2017-11-20 16:10 ` Cyril Hrubis
2017-11-20 16:48 ` Tom Gall
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=7a73bb41-8372-57d3-2aca-6840ca231167@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=shuahkh@osg.samsung.com \
--cc=stable@vger.kernel.org \
--cc=tom.gall@linaro.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®