linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	sboyd@codeaurora.org, prarit@redhat.com, skannan@codeaurora.org,
	Srivatsa Bhat <srivatsa@mit.edu>
Subject: Re: [PATCH V5 00/14] cpufreq: Don't loose cpufreq history on CPU hotplug
Date: Tue, 19 May 2015 07:57:46 +0530	[thread overview]
Message-ID: <20150519022746.GE5102@linux> (raw)
In-Reply-To: <5515479.9CSMtpamVj@vostro.rjw.lan>

On 19-05-15, 02:34, Rafael J. Wysocki wrote:
> I've applied patches [1-6/14] from your previous series.  Should I replace them
> with the new ones?

Never realised that you have applied more of these. Yeah, apply
everything other than 1-6. Thanks.

-- 
viresh

      reply	other threads:[~2015-05-19  2:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  5:13 [PATCH V5 00/14] cpufreq: Don't loose cpufreq history on CPU hotplug Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 01/14] cpufreq: Create for_each_{in}active_policy() Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 02/14] cpufreq: Don't clear cpufreq_cpu_data and policy list for inactive policies Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 03/14] cpufreq: Get rid of cpufreq_cpu_data_fallback Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 04/14] cpufreq: Don't traverse all active policies to find policy for a cpu Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 05/14] cpufreq: Manage governor usage history with 'policy->last_governor' Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 06/14] cpufreq: Mark policy->governor = NULL for inactive policies Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 07/14] cpufreq: Don't allow updating inactive policies from sysfs Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 08/14] cpufreq: Track cpu managing sysfs kobjects separately Viresh Kumar
2015-05-22 23:29   ` Rafael J. Wysocki
2015-05-18  5:13 ` [PATCH V5 09/14] cpufreq: add/remove sysfs links via cpufreq_add_remove_dev_symlink() Viresh Kumar
2015-05-22 23:28   ` Rafael J. Wysocki
2015-05-23  3:41     ` Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 10/14] cpufreq: Stop migrating sysfs files on hotplug Viresh Kumar
2015-05-23  3:45   ` (unknown), Viresh Kumar
2015-05-23  4:34     ` [PATCH V6 10/14] cpufreq: Remove cpufreq_update_policy() Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 11/14] " Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 12/14] cpufreq: Initialize policy->kobj while allocating policy Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 13/14] cpufreq: Call cpufreq_policy_put_kobj() from cpufreq_policy_free() Viresh Kumar
2015-05-18  5:13 ` [PATCH V5 14/14] cpufreq: Restart governor as soon as possible Viresh Kumar
2015-05-19  0:34 ` [PATCH V5 00/14] cpufreq: Don't loose cpufreq history on CPU hotplug Rafael J. Wysocki
2015-05-19  2:27   ` Viresh Kumar [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=20150519022746.GE5102@linux \
    --to=viresh.kumar@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@codeaurora.org \
    --cc=skannan@codeaurora.org \
    --cc=srivatsa@mit.edu \
    /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).