From: Shuah Khan <shuah@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 0/4] selftest: cpufreq: Add support for cpufreq framework
Date: Fri, 13 Jan 2017 15:35:20 -0700 [thread overview]
Message-ID: <bde954c8-d581-aa9d-a64d-2ca94e794f2f@kernel.org> (raw)
In-Reply-To: <cover.1484289212.git.viresh.kumar@linaro.org>
On 01/12/2017 11:36 PM, Viresh Kumar wrote:
> Hi,
>
> This patchset adds support for cpufreq selftests to the kernel selftest
> framework. More details can be found on individual patches.
>
> These are all tested after installation of selftests on ARM Dual A15
> core Exynos platform.
>
> The content of the output file for the basic tests looks like this:
> http://pastebin.com/nBY9AfD5 .
>
> --
> viresh
Hi Viresh,
Could you please add .gitignore for generated files. You can
send that as a separate patch and don't have to resend the
series.
thanks,
-- Shuah
>
> Viresh Kumar (4):
> selftest: cpufreq: Add support for cpufreq tests
> selftest: cpufreq: Add suspend/resume/hibernate support
> selftest: cpufreq: Add support to test cpufreq modules
> selftest: cpufreq: Add special tests
>
> tools/testing/selftests/Makefile | 1 +
> tools/testing/selftests/cpufreq/Makefile | 8 +
> tools/testing/selftests/cpufreq/cpu.sh | 84 ++++++++
> tools/testing/selftests/cpufreq/cpufreq.sh | 241 ++++++++++++++++++++++
> tools/testing/selftests/cpufreq/governor.sh | 153 ++++++++++++++
> tools/testing/selftests/cpufreq/main.sh | 194 ++++++++++++++++++
> tools/testing/selftests/cpufreq/module.sh | 243 +++++++++++++++++++++++
> tools/testing/selftests/cpufreq/special-tests.sh | 115 +++++++++++
> 8 files changed, 1039 insertions(+)
> create mode 100644 tools/testing/selftests/cpufreq/Makefile
> create mode 100755 tools/testing/selftests/cpufreq/cpu.sh
> create mode 100755 tools/testing/selftests/cpufreq/cpufreq.sh
> create mode 100755 tools/testing/selftests/cpufreq/governor.sh
> create mode 100755 tools/testing/selftests/cpufreq/main.sh
> create mode 100755 tools/testing/selftests/cpufreq/module.sh
> create mode 100755 tools/testing/selftests/cpufreq/special-tests.sh
>
next prev parent reply other threads:[~2017-01-13 22:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 6:36 [PATCH 0/4] selftest: cpufreq: Add support for cpufreq framework Viresh Kumar
2017-01-13 6:36 ` [PATCH 1/4] selftest: cpufreq: Add support for cpufreq tests Viresh Kumar
2017-01-13 6:36 ` [PATCH 2/4] selftest: cpufreq: Add suspend/resume/hibernate support Viresh Kumar
2017-01-13 6:36 ` [PATCH 3/4] selftest: cpufreq: Add support to test cpufreq modules Viresh Kumar
2017-01-13 6:36 ` [PATCH 4/4] selftest: cpufreq: Add special tests Viresh Kumar
2017-01-13 22:35 ` Shuah Khan [this message]
2017-01-16 3:48 ` [PATCH 0/4] selftest: cpufreq: Add support for cpufreq framework Viresh Kumar
2017-01-17 21:00 ` Shuah Khan
2017-01-19 17:36 ` Shuah Khan
2017-01-20 5:40 ` [PATCH] selftest: cpufreq: Update MAINTAINERS file Viresh Kumar
2017-02-06 10:38 ` Viresh Kumar
2017-02-06 19:22 ` Shuah Khan
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=bde954c8-d581-aa9d-a64d-2ca94e794f2f@kernel.org \
--to=shuah@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).