From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/4] intel_pstate updates
Date: Mon, 21 Oct 2013 15:40:04 -0700 [thread overview]
Message-ID: <5265AD44.6010805@gmail.com> (raw)
In-Reply-To: <4839646.Ilm2lvf4gq@vostro.rjw.lan>
On 10/21/2013 03:46 PM, Rafael J. Wysocki wrote:
> On Monday, October 21, 2013 09:29:58 AM Dirk Brandewie wrote:
>> Forgot to add this patch set is based on linux-pm/bleeding-edge
>> commit 1a1da369261c3ee2c3caa078b6ace46adcdffbb6
>
> So do I assume correctly that is is all 3.13 material?
>
> Or are patches [1-2/4] for 3.12?
>
1-2 are for 3.12
3-4 are for 3.13 Baytrail support requires ther refactoring to take
into account that the P state enumeration is different on Baytrail.
> Rafael
>
prev parent reply other threads:[~2013-10-21 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 16:20 [PATCH 0/4] intel_pstate updates dirk.brandewie
2013-10-21 16:20 ` [PATCH 1/4] cpufreq: intel_pstate: Improve accuracy by not truncating until final result dirk.brandewie
2013-10-21 20:53 ` Brennan Shacklett
2013-10-21 16:20 ` [PATCH 2/4] cpufreq/intel_pstate: Correct calculation of min pstate value dirk.brandewie
2013-10-21 16:20 ` [PATCH 3/4] cpufreq/intel_pstate: Refactor driver to support CPUs with different MSR layouts dirk.brandewie
2013-10-21 16:20 ` [PATCH 4/4] cpufreq/intel_pstate: Add Baytrail support dirk.brandewie
2013-10-21 16:29 ` [PATCH 0/4] intel_pstate updates Dirk Brandewie
2013-10-21 22:46 ` Rafael J. Wysocki
2013-10-21 22:40 ` Dirk Brandewie [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=5265AD44.6010805@gmail.com \
--to=dirk.brandewie@gmail.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).