From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] cpufreq-dt: add suspend frequency support
Date: Thu, 17 Sep 2015 07:44:53 +0900 [thread overview]
Message-ID: <55F9F0E5.7000805@kernel.org> (raw)
In-Reply-To: <20150908051053.GA18554@linux>
On 09/08/15 14:10, Viresh Kumar wrote:
> On 08-09-15, 13:48, Krzysztof Kozlowski wrote:
>> Somehow my mind stuck on solving Exynos4x12 cpufreq issues.
>>
>> Right, it should go through Rafael's, probably except DTS patch (4/4)
>> because it depends on previous DTS changes. These changes are still in
>> arm-soc, not in Linus' tree [0].
>
> That's bad :(
>
> Anyway, 4/4 is kind of independent to this series, in the sense that
> it wouldn't harm even if it gets applied separately.
>
> So, go ahead and apply 4/4 to Samsung's tree and rest of this can be
> picked by Rafael.
>
Applied 4/4 into samsung tree, thanks.
- Kukjin
prev parent reply other threads:[~2015-09-16 22:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 15:41 [PATCH v4 0/4] cpufreq-dt: add suspend frequency support Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` [PATCH v4 1/4] PM / OPP: add dev_pm_opp_get_suspend_opp() helper Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` [PATCH v4 2/4] cpufreq: allow cpufreq_generic_suspend() to work without suspend frequency Bartlomiej Zolnierkiewicz
2015-09-07 15:41 ` [PATCH v4 3/4] cpufreq-dt: add suspend frequency support Bartlomiej Zolnierkiewicz
2015-09-08 2:45 ` Viresh Kumar
2015-09-07 15:41 ` [PATCH v4 4/4] ARM: dts: add suspend opp to exynos4412 Bartlomiej Zolnierkiewicz
2015-09-08 0:34 ` Krzysztof Kozlowski
2015-09-08 2:46 ` [PATCH v4 0/4] cpufreq-dt: add suspend frequency support Viresh Kumar
2015-09-08 3:56 ` Krzysztof Kozlowski
2015-09-08 4:20 ` Viresh Kumar
2015-09-08 4:48 ` Krzysztof Kozlowski
2015-09-08 5:10 ` Viresh Kumar
2015-09-16 22:44 ` Kukjin Kim [this message]
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=55F9F0E5.7000805@kernel.org \
--to=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).