From: dirk.brandewie@gmail.com
To: linux-pm@vger.kernel.org
Cc: rjw@rjwysocki.net, Dirk Brandewie <dirk.j.brandewie@intel.com>
Subject: [PATCH 00/11] intel_pstate updates
Date: Fri, 18 Jul 2014 08:37:16 -0700 [thread overview]
Message-ID: <1405697848-13546-1-git-send-email-dirk.j.brandewie@intel.com> (raw)
From: Dirk Brandewie <dirk.j.brandewie@intel.com>
These patches have been in the development branch used by Stratos,
Doug and myself for a long time. I had hoped to batch them up with
other functional changes that are under development but those changes
are still under active discussion and there is no reason to hold these
changes up.
Based on v3.16-rc5 commit 1795cd9b3a91d4b5473c97f491d63892442212ab
Stratos Karafotis (11):
cpufreq: intel_pstate: Make intel_pstate_kobject and debugfs_parent
locals
cpufreq: intel_pstate: Remove unnecessary type casting in div_s64()
call
cpufreq: intel_pstate: Add missing blank lines after declarations
cpufreq: intel_pstate: Fit code in a single line where possible
cpufreq: intel_pstate: Cleanup parentheses
cpufreq: intel_pstate: Remove unnecessary intermediate variable
sample_time
cpufreq: intel_pstate: Align multiple lines to open parenthesis
cpufreq: intel_pstate: Disable interrupts during MSRs reading
cpufreq: intel_pstate: Simplify P state adjustment logic.
cpufreq: intel_pstate: Remove core_pct rounding
cpufreq: intel_pstate: Keep values in aperf/mperf in full precision
drivers/cpufreq/intel_pstate.c | 131 +++++++++++++++++------------------------
1 file changed, 53 insertions(+), 78 deletions(-)
--
1.9.3
next reply other threads:[~2014-07-18 15:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 15:37 dirk.brandewie [this message]
2014-07-18 15:37 ` [PATCH 01/11] cpufreq: intel_pstate: Make intel_pstate_kobject and debugfs_parent locals dirk.brandewie
2014-07-18 15:37 ` [PATCH 02/11] cpufreq: intel_pstate: Remove unnecessary type casting in div_s64() call dirk.brandewie
2014-07-18 15:37 ` [PATCH 03/11] cpufreq: intel_pstate: Add missing blank lines after declarations dirk.brandewie
2014-07-18 15:37 ` [PATCH 04/11] cpufreq: intel_pstate: Fit code in a single line where possible dirk.brandewie
2014-07-18 15:37 ` [PATCH 05/11] cpufreq: intel_pstate: Cleanup parentheses dirk.brandewie
2014-07-18 15:37 ` [PATCH 06/11] cpufreq: intel_pstate: Remove unnecessary intermediate variable sample_time dirk.brandewie
2014-07-18 15:37 ` [PATCH 07/11] cpufreq: intel_pstate: Align multiple lines to open parenthesis dirk.brandewie
2014-07-18 15:37 ` [PATCH 08/11] cpufreq: intel_pstate: Disable interrupts during MSRs reading dirk.brandewie
2014-07-18 15:37 ` [PATCH 09/17] cpufreq: intel_pstate: Keep values in aperf/mperf in full precision dirk.brandewie
2014-07-18 15:37 ` [PATCH 09/11] cpufreq: intel_pstate: Simplify P state adjustment logic dirk.brandewie
2014-07-18 15:37 ` [PATCH 10/11] cpufreq: intel_pstate: Remove core_pct rounding dirk.brandewie
2014-07-18 15:37 ` [PATCH 11/11] cpufreq: intel_pstate: Keep values in aperf/mperf in full precision dirk.brandewie
2014-07-19 20:31 ` [PATCH 00/11] intel_pstate updates Rafael J. Wysocki
2014-07-19 21:01 ` Stratos Karafotis
2014-07-19 21:54 ` Rafael J. Wysocki
2014-07-19 22:05 ` Stratos Karafotis
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=1405697848-13546-1-git-send-email-dirk.j.brandewie@intel.com \
--to=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-pm@vger.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).