From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: inderpal.singh@linaro.org, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linaro-dev@lists.linaro.org, patches@linaro.org,
robin.randhawa@arm.com, Steve.Bannister@arm.com,
Liviu.Dudau@arm.com
Subject: Re: [PATCH 1/2] cpufreq: Set policy->related_cpus to atleast policy->cpus
Date: Tue, 29 Jan 2013 12:51:23 +0100 [thread overview]
Message-ID: <2215618.GPIWS1OcnB@vostro.rjw.lan> (raw)
In-Reply-To: <d6827976a56d429848ab8ababa2779a21c68d65f.1359434113.git.viresh.kumar@linaro.org>
On Tuesday, January 29, 2013 10:09:59 AM Viresh Kumar wrote:
> With the addition of following patch, related_cpus is required to be set by
> cpufreq platform drivers:
>
> commit c1070fd743533efb54e98142252283583f379190
> Author: Viresh Kumar <viresh.kumar@linaro.org>
> Date: Mon Jan 14 13:23:04 2013 +0000
>
> cpufreq: Simplify cpufreq_add_dev()
>
I've dropped this one in the meantime.
Can you please fold the $subject patch into "cpufreq: Simplify cpufreq_add_dev()"
and post the result instead? That surely will be less confusing?
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-01-29 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 4:39 Viresh Kumar
2013-01-29 4:40 ` [PATCH 2/2] Revert "cpufreq: Don't use cpu removed during cpufreq_driver_unregister" Viresh Kumar
2013-01-29 4:41 ` [PATCH 1/2] cpufreq: Set policy->related_cpus to atleast policy->cpus Viresh Kumar
2013-01-29 11:51 ` Rafael J. Wysocki [this message]
2013-01-29 14:30 ` Viresh Kumar
2013-01-29 21:50 ` Rafael J. Wysocki
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=2215618.GPIWS1OcnB@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=inderpal.singh@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=robin.randhawa@arm.com \
--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
all inboxes | Powered by JetHome®