From: Shuah Khan <shuah@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
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 <shuahkh@osg.samsung.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 0/4] selftest: cpufreq: Add support for cpufreq framework
Date: Thu, 19 Jan 2017 10:36:36 -0700 [thread overview]
Message-ID: <c3cd3310-7a12-134e-3c5a-c5fcacc6821d@kernel.org> (raw)
In-Reply-To: <ca6812e9-88be-17b0-be3c-47681ab0653b@kernel.org>
On 01/17/2017 02:00 PM, Shuah Khan wrote:
> On 01/15/2017 08:48 PM, Viresh Kumar wrote:
>> On 13-01-17, 15:35, Shuah Khan wrote:
>>> Could you please add .gitignore for generated files. You can
>>> send that as a separate patch and don't have to resend the
>>> series.
>>
>> Hi Shuah,
>>
>>>> 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 +++++++++++
>>
>> All I have are .sh files and no intermediate files are generated.
>> Perhaps I don't need any .gitignore entries ?
>>
>
> Never mind. There is no need to do .gitignore.
>
Thanks for these tests. Applied the series to linux-kselftest next
for 4.11
thanks,
-- Shuah
next prev parent reply other threads:[~2017-01-19 17:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 6:36 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 ` [PATCH 0/4] selftest: cpufreq: Add support for cpufreq framework Shuah Khan
2017-01-16 3:48 ` Viresh Kumar
2017-01-17 21:00 ` Shuah Khan
2017-01-19 17:36 ` Shuah Khan [this message]
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=c3cd3310-7a12-134e-3c5a-c5fcacc6821d@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=shuahkh@osg.samsung.com \
--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
Powered by JetHome