linux-kernel - Re: [PATCH 0/2] Clock changes for supporting CPUFreq on Exynos5250

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

Message-ID: <51B15A19.2020403@linaro.org>
Date:	Fri, 07 Jun 2013 09:27:13 +0530
From:	Tushar Behera <tushar.behera@...aro.org>
To:	Mike Turquette <mturquette@...aro.org>
CC:	linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
	kgene.kim@...sung.com, thomas.abraham@...aro.org,
	patches@...aro.org
Subject: Re: [PATCH 0/2] Clock changes for supporting CPUFreq on Exynos5250

>> Would it be possible for you to queue them for 3.10-rc? These two
>> patches are sufficient for cpufreq to work on Arndale board. It would be
>> nice to have cpufreq working on 3.10 kernel.
>>
> 
> I only want to take bug fixes into the -rc's.  Did cpufreq work on
> Arndale in v3.10?  If it did then this is a regression and can be fixed.
> If this is a new feature however I'll keep the patches in clk-next.
> 

This fixes a regression as cpufreq was working for EXYNOS5250 based
systems before migration to CCF.

Though Arndale support was added during 3.10, this holds good for other
EXYNOS5250 based systems.

-- 
Tushar Behera
--
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/