linux-kernel - Re: [PATCH 0/4] selftest: cpufreq: Add support for cpufreq framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 17 Jan 2017 14:00:00 -0700
From:   Shuah Khan <shuah@...nel.org>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     Rafael Wysocki <rjw@...ysocki.net>, linaro-kernel@...ts.linaro.org,
        linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
        Vincent Guittot <vincent.guittot@...aro.org>,
        linux-kselftest@...r.kernel.org,
        Shuah Khan <shuahkh@....samsung.com>,
        Shuah Khan <shuah@...nel.org>
Subject: Re: [PATCH 0/4] selftest: cpufreq: Add support for cpufreq framework

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,
-- Shuah