From: Tushar Behera <tushar.behera@linaro.org>
To: Mike Turquette <mturquette@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
kgene.kim@samsung.com, thomas.abraham@linaro.org,
patches@linaro.org
Subject: Re: [PATCH 0/2] Clock changes for supporting CPUFreq on Exynos5250
Date: Thu, 06 Jun 2013 14:32:18 +0530 [thread overview]
Message-ID: <51B0501A.8070004@linaro.org> (raw)
In-Reply-To: <20130529224203.6058.75266@quantum>
On 05/30/2013 04:12 AM, Mike Turquette wrote:
> Quoting Tushar Behera (2013-05-27 22:38:44)
>> On 05/17/2013 11:25 AM, Tushar Behera wrote:
>>> With the use of common clock framework, CPUFreq driver on EXYNOS5250 now
>>> requires a few changes in clocks.
>>>
>>> Tested on Exynos5250 based Arndale board.
>>> The patches are based on v3.10-rc1.
>>>
>>> Tushar Behera (2):
>>> clk: exynos5250: Update cpufreq related clocks for EXYNOS5250
>>> clk: exynos5250: Add sclk_mpll to the parent list of mout_cpu clock
>>>
>>> drivers/clk/samsung/clk-exynos5250.c | 8 ++++----
>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>>
>>
>> Any comments on this series?
>>
>
> I've taken both patches into clk-next.
>
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.
> Regards,
> Mike
>
>> --
>> Tushar Behera
--
Tushar Behera
next prev parent reply other threads:[~2013-06-06 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 5:55 [PATCH 0/2] Clock changes for supporting CPUFreq on Exynos5250 Tushar Behera
2013-05-17 5:55 ` [PATCH 1/2] clk: exynos5250: Update cpufreq related clocks for EXYNOS5250 Tushar Behera
2013-05-17 5:55 ` [PATCH 2/2] clk: exynos5250: Add sclk_mpll to the parent list of mout_cpu clock Tushar Behera
2013-05-28 5:38 ` [PATCH 0/2] Clock changes for supporting CPUFreq on Exynos5250 Tushar Behera
2013-05-29 22:42 ` Mike Turquette
2013-06-06 9:02 ` Tushar Behera [this message]
[not found] ` <20130606195156.10233.37021@quantum>
2013-06-07 3:57 ` Tushar Behera
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=51B0501A.8070004@linaro.org \
--to=tushar.behera@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=patches@linaro.org \
--cc=thomas.abraham@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;
as well as URLs for NNTP newsgroup(s).