[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7F8EB1E5A1A71643ACAD0928E03FFDE90E3D796C79@USMBX1.msg.corp.akamai.com>
Date: Tue, 9 Dec 2014 16:29:57 -0500
From: "Young, David" <dayoung@...mai.com>
To: Shuah Khan <shuahkhan@...il.com>
CC: Greg KH <gregkh@...uxfoundation.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"shuahkh@....samsung.com" <shuahkh@....samsung.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: selftests: question about git repos containing selftest.
Thanks for clearing this up, very helpful!
-dave
-----Original Message-----
From: Shuah Khan [mailto:shuahkhan@...il.com]
Sent: Tuesday, December 09, 2014 4:27 PM
To: Young, David
Cc: Greg KH; linux-api@...r.kernel.org; shuahkh@....samsung.com; linux-kernel@...r.kernel.org
Subject: Re: selftests: question about git repos containing selftest.
On Tue, Dec 9, 2014 at 2:08 PM, Young, David <dayoung@...mai.com> wrote:
>
>> Do you have specific patches in linux-next that you have questions about?
>
> Mostly I am interested in executing kselftests via something like autotest or Hudson/jenkins as a quick smoketest. I understand it's still very much an in-progress feature, but would like the closest thing to a stable set of tests to regularly clone and use. I suppose I could just wait for whatever makes it into mainline, but I'm interested in seeing the planned test coverage and test output so that I can write appropriate "glue" for use with a continuous-integration test system.
>
David,
Please follow fixes branch for patches that are going to be in the next mainline release. I am planning to create devel or experimental branch to make my next revision install target patches available for early testing for people that want to play with work in progress. Hope this is helpful.
thanks,
-- Shuah
Powered by blists - more mailing lists