[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <551D1692.1050302@redhat.com>
Date: Thu, 02 Apr 2015 06:14:42 -0400
From: Prarit Bhargava <prarit@...hat.com>
To: John Stultz <john.stultz@...aro.org>
CC: lkml <linux-kernel@...r.kernel.org>,
Shuah Khan <shuahkh@....samsung.com>,
Thomas Gleixner <tglx@...utronix.de>,
Richard Cochran <richardcochran@...il.com>,
Tyler Baker <tyler.baker@...aro.org>
Subject: Re: [PATCH 1/2] kselftests: timers: Make set-timer-lat fail more
gracefully for !CAP_WAKE_ALARM
On 03/26/2015 12:29 PM, John Stultz wrote:
> On Thu, Mar 26, 2015 at 4:31 AM, Prarit Bhargava <prarit@...hat.com> wrote:
>> On 03/25/2015 07:44 PM, John Stultz wrote:
>>> + printf("%-22s %s missing CAP_WAKE_ALARM? : [UNSUPPORTED]\n",
>>> + clockstring(clock_id),
>>> + flags ? "ABSTIME":"RELTIME");
>>
>> Something to think about: Do you want to write these tests to be more human
>> readable or machine readable? In theory with awk I guess it doesn't matter too
>> much, however, it is something that we should think about moving forward.
>
> So this came up at ELC in a few discussions. Right now there isn't any\
Sorry, I'm not familiar with ELC? What is that Acronym for?
> established output format, but there's some nice and simple
> infrastructure for counting pass/fails.
Okay that's great.
>
> However, in talking to Tyler, I know he has started looking at how to
> integrate the selftests into our automated infrastructure and was
> interested in how we improve the output parsing for reports. So there
> is interest in improving this, and I'm open to whatever changes might
> be needed (adding extra arguments to the test to put them into "easy
> parse" mode or whatever).
Thanks John.
P.
>
> thanks
> -john
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists