linux-kernel - Re: [PATCH V2] Fix problem with cpufreq_ondemand or cpufreq

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] [day] [month] [year] [list]

Message-ID: <CAKohponf3dCYvEaZAUU4_2zRP+z2nPfskiQmykW4T_TxPG3J+A@mail.gmail.com>
Date:	Wed, 2 Jan 2013 09:42:37 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	cpufreq@...r.kernel.org, Linux PM list <linux-pm@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2] Fix problem with cpufreq_ondemand or cpufreq_conservative

On 2 January 2013 09:40, Larry Finger <Larry.Finger@...inger.net> wrote:
>>> Index: wireless-testing-new/drivers/cpufreq/cpufreq_governor.c
>>
>>
>> How are you creating these patches? wireless-testing-new (linux directory
>> names)
>> aren't supposed to be present here.

You Missed this one?

> I was not adding myself - my name is not Alexander Clouter. When we were
> creating a new module, I got the author from the module that
> cpufreq_governor was originally a part. Perhaps I got the name wrong.

Err.. I read it wrong... sorry :)
--
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/