From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/14] cpufreq: create & use cpufreq_generic_init() routine
Date: Thu, 22 Aug 2013 01:20:34 +0200 [thread overview]
Message-ID: <1493410.kWm56FEZ0a@vostro.rjw.lan> (raw)
In-Reply-To: <cover.1377093938.git.viresh.kumar@linaro.org>
On Wednesday, August 21, 2013 08:12:19 PM Viresh Kumar wrote:
> Many CPUFreq drivers for SMP system (where all cores share same clock lines), do
> similar stuff in their ->init() part.
>
> This patch creates a generic routine in cpufreq core which can be used by these
> so that we can remove some redundant code. And later part of patchset makes
> other drivers use this infrastructure.
>
> Many drivers which weren't setting policy->cpus haven't been updated as they
> might have separate clocks for CPUs and setting all CPUs in policy->cpus may
> corrupt them..
>
> This is Sixth part of my cleanup work for CPUFreq, first five are (And
> obviously its rebased over them):
OK, so the plan for merging this will be that we'll put 1 into linux-next
and add 2 to it after a few days etc. to give people a chance to test one
set of changes before going to the next one.
> 1: cpufreq: Introduce cpufreq_table_validate_and_show()
> https://lkml.org/lkml/2013/8/8/263
So perhaps we can *try* to push the above for 3.12 if it doesn't breaks
stuff left and right.
Can you please resend it with all of the ACKs collected so far?
Thanks,
Rafael
next prev parent reply other threads:[~2013-08-21 23:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 14:42 [PATCH 00/14] cpufreq: create & use cpufreq_generic_init() routine Viresh Kumar
2013-08-21 14:42 ` [PATCH 01/14] cpufreq: create " Viresh Kumar
2013-08-21 14:42 ` [PATCH 02/14] cpufreq: cpu0: use " Viresh Kumar
2013-08-21 14:42 ` [PATCH 03/14] cpufreq: dbx500: " Viresh Kumar
2013-08-21 23:00 ` Linus Walleij
2013-08-21 14:42 ` [PATCH 04/14] cpufreq: exynos: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 05/14] cpufreq: imx6q: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 06/14] cpufreq: kirkwood: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 07/14] cpufreq: maple: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 08/14] cpufreq: pasemi: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 09/14] cpufreq: pmac64: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 10/14] cpufreq: s3c: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 11/14] cpufreq: s5pv210: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 12/14] cpufreq: sa11x0: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 13/14] cpufreq: spear: " Viresh Kumar
2013-08-21 14:42 ` [PATCH 14/14] cpufreq: tegra: " Viresh Kumar
2013-08-21 23:20 ` Rafael J. Wysocki [this message]
2013-08-22 4:47 ` [PATCH 00/14] cpufreq: create & " Viresh Kumar
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=1493410.kWm56FEZ0a@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=viresh.kumar@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