linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: rjw@sisk.pl
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
	cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/5] CPUFreq: Last set of updates for 3.13
Date: Wed, 11 Sep 2013 15:43:06 +0530	[thread overview]
Message-ID: <cover.1378893296.git.viresh.kumar@linaro.org> (raw)

Hi Rafael,

I really tried to stop after you asked me to, but still got few more patches..
These are very minor changes and a fairly smaller patchset..

I have rebased this over your linux-next branch

7c218b1 Merge branch 'acpi-bind-next' into linux-next

and tested over my exynos board.. I don't expect them to do any crappy stuff..

You can include these first (if they look fine) and then I will send all other
patches that I have queued up for 3.13.. I will send all of them in one lot,
with partition numbers mentioned (i.e. patches that should go together) and then
you can apply them the way you wish.. Set by set or all at once..

Thanks..

Viresh Kumar (5):
  cpufreq: Optimize cpufreq_frequency_table_verify()
  cpufreq: rename __cpufreq_set_policy() as cpufreq_set_policy()
  cpufreq: rewrite cpufreq_driver->flags using shift operator
  cpufreq: use cpufreq_driver->flags to mark
    CPUFREQ_HAVE_GOVERNOR_PER_POLICY
  cpufreq: add new routine cpufreq_verify_within_cpu_limits()

 drivers/cpufreq/arm_big_little.c     |  4 ++--
 drivers/cpufreq/cpufreq-nforce2.c    |  4 +---
 drivers/cpufreq/cpufreq.c            | 24 ++++++++++-------------
 drivers/cpufreq/cpufreq_governor.h   |  5 ++++-
 drivers/cpufreq/davinci-cpufreq.c    |  4 +---
 drivers/cpufreq/freq_table.c         | 27 +++++++++++++-------------
 drivers/cpufreq/integrator-cpufreq.c |  9 ++-------
 drivers/cpufreq/intel_pstate.c       |  4 +---
 drivers/cpufreq/longrun.c            |  4 +---
 drivers/cpufreq/pcc-cpufreq.c        |  3 +--
 drivers/cpufreq/sh-cpufreq.c         |  7 ++-----
 drivers/cpufreq/unicore2-cpufreq.c   |  4 +---
 include/linux/cpufreq.h              | 37 ++++++++++++++++++++++--------------
 13 files changed, 62 insertions(+), 74 deletions(-)

-- 
1.7.12.rc2.18.g61b472e


             reply	other threads:[~2013-09-11 10:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 10:13 Viresh Kumar [this message]
2013-09-11 10:13 ` [PATCH 1/5] cpufreq: Optimize cpufreq_frequency_table_verify() Viresh Kumar
2013-09-11 10:13 ` [PATCH 2/5] cpufreq: rename __cpufreq_set_policy() as cpufreq_set_policy() Viresh Kumar
2013-09-11 10:13 ` [PATCH 3/5] cpufreq: rewrite cpufreq_driver->flags using shift operator Viresh Kumar
2013-09-11 10:13 ` [PATCH 4/5] cpufreq: use cpufreq_driver->flags to mark CPUFREQ_HAVE_GOVERNOR_PER_POLICY Viresh Kumar
2013-09-11 10:13 ` [PATCH 5/5] cpufreq: add new routine cpufreq_verify_within_cpu_limits() Viresh Kumar
2013-09-11 10:53 ` [PATCH 0/5] CPUFreq: Last set of updates for 3.13 Amit Kucheria
2013-09-11 10:59   ` 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=cover.1378893296.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --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=rjw@sisk.pl \
    /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).