From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/3] cpufreq: intel_pstate: Fixes related to limis
Date: Wed, 01 Mar 2017 00:00:05 +0100 [thread overview]
Message-ID: <2326598.n0dkg1GrdM@aspire.rjw.lan> (raw)
In-Reply-To: <2694426.SgxlQuL17D@aspire.rjw.lan>
Hi,
On Tuesday, February 28, 2017 02:13:30 PM Rafael J. Wysocki wrote:
> Hi,
>
> Both fix some utter confusion in the sysfs interface.
>
> The first one makes intel_pstate_update_policies() end up with limits set to
> the same value that it was set to initially.
>
> The second one avoids reinitializing limits in intel_pstate_set_policy() when
> the moon phase is right and the wind blows from a specific direction.
Resending an updated series, because patch [1/3] required a rework and I found
one more problem (addressed by patch [3/3]).
Thanks,
Rafael
next prev parent reply other threads:[~2017-02-28 23:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 13:13 [PATCH 0/2] cpufreq: intel_pstate: Two fixes " Rafael J. Wysocki
2017-02-28 13:14 ` [PATCH 1/2] cpufreq: intel_pstate: Fix global settings in active mode Rafael J. Wysocki
2017-02-28 22:21 ` Rafael J. Wysocki
2017-02-28 13:16 ` [PATCH 2/2] cpufreq: intel_pstate: Do not reinit performance limits in ->setpolicy Rafael J. Wysocki
2017-02-28 23:00 ` Rafael J. Wysocki [this message]
2017-02-28 23:07 ` [PATCH v2 1/3] cpufreq: intel_pstate: Fix global settings in active mode Rafael J. Wysocki
2017-02-28 23:09 ` [PATCH v2 2/3] cpufreq: intel_pstate: Do not reinit performance limits in ->setpolicy Rafael J. Wysocki
2017-03-02 17:18 ` Rafael J. Wysocki
2017-03-02 17:22 ` Rafael J. Wysocki
2017-03-02 22:29 ` [Update][PATCH v3 " Rafael J. Wysocki
2017-03-29 22:01 ` Doug Smythies
2017-03-29 22:16 ` Doug Smythies
2017-03-29 22:17 ` Rafael J. Wysocki
2017-02-28 23:11 ` [PATCH v2 3/3] cpufreq: intel_pstate: Fix intel_pstate_verify_policy() 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=2326598.n0dkg1GrdM@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
/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®