From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 2/2] cpufreq: intel_pstate: Fix set_policy interface for no_turbo
Date: Wed, 08 Jun 2016 08:39:53 -0700 [thread overview]
Message-ID: <1465400393.25099.8.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0iUvAxH6kJYuKO0Ty7WiHtTPMUSOoMYFsLR26evvu_jCQ@mail.gmail.com>
On Wed, 2016-06-08 at 03:24 +0200, Rafael J. Wysocki wrote:
> >
[...]
> On Wed, Jun 8, 2016 at 3:10 AM, Rafael J. Wysocki <rafael@kernel.org>
> wrote:
> > > policy->cpuinfo.max_freq = limits->turbo_disabled ?
> > > cpu->pstate.max_pstate : cpu->pstate.turbo_pstate;
> > > policy->cpuinfo.max_freq *= cpu->pstate.scaling;
> > But of course without GMail-induced whitespace breakage.
> So I went on and changed it this way before applying. Please check
> the result in bleeding-edge.
Checked. Looks good.
Thanks,
Srinivas
prev parent reply other threads:[~2016-06-08 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 0:38 [PATCH 1/2] cpufreq: intel_pstate: Move limits->max_perf to correct position Srinivas Pandruvada
2016-06-08 0:38 ` [PATCH 2/2] cpufreq: intel_pstate: Fix set_policy interface for no_turbo Srinivas Pandruvada
2016-06-08 0:42 ` Rafael J. Wysocki
2016-06-08 0:48 ` Srinivas Pandruvada
2016-06-08 0:50 ` Rafael J. Wysocki
2016-06-08 0:55 ` Srinivas Pandruvada
2016-06-08 1:06 ` Rafael J. Wysocki
2016-06-08 1:10 ` Rafael J. Wysocki
2016-06-08 1:24 ` Rafael J. Wysocki
2016-06-08 15:39 ` Srinivas Pandruvada [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=1465400393.25099.8.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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).