linux-kernel - Re: [PATCH 0/2] cpufreq: fix transition

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: <CAKohponbmEDmq3c85h=oSNKTfy+BcS0SLVdGp42osOrGQJha9g@mail.gmail.com>
Date:	Sat, 14 Sep 2013 09:59:15 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
	Patch Tracking <patches@...aro.org>,
	"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] cpufreq: fix transition_ongoing count for powernow-k8

On 14 September 2013 05:12, Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Friday, September 13, 2013 06:29:37 PM Viresh Kumar wrote:
>> This has been running in my mind since few days... That we have fixed cpufreq
>> core and all other drivers for transition serialization but what about
>> powernow-k8? It is somewhat special (even more than exynos5440).. It queues a
>> work from ->target() and may or maynot send notifications at all..
>>
>> Finally I have got a solution now (detailed logs in the patch)..
>> These must go with following patchset:
>
> The "must go" here is a totally wrong way of speaking about things, because I'm
> not sure I'll take this patch series yet.
>
>> https://lkml.org/lkml/2013/9/12/173

The "must go" was about keeping all four patches together, rather than
forcing you to take them all..

Sorry for the confusion..
--
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/