From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: dirk.brandewie@gmail.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
Dirk Brandewie <dirk.j.brandewie@intel.com>
Subject: Re: [PATCH 0/5] updates for intel_pstate
Date: Thu, 08 May 2014 14:08:30 -0700 [thread overview]
Message-ID: <536BF24E.1000709@gmail.com> (raw)
In-Reply-To: <3320314.vMXib5RYFF@vostro.rjw.lan>
On 05/08/2014 01:30 PM, Rafael J. Wysocki wrote:
> On Thursday, May 08, 2014 12:57:22 PM dirk.brandewie@gmail.com wrote:
>> From: Dirk Brandewie <dirk.j.brandewie@intel.com>
>>
>> Patches 1-4 are bugfixes. Patch 4 specifically removes the wreckage
>> caused by C0 tracking change.
>
> I would appreciate sending such stuff before the -rc4 time frame.
Agreed.
Patch 1 is a resend the others were sent as soon as they were ready/tested
>
>> Patch 5 Adds new CPU IDs for the Broadwell processors.
>>
>> Dirk Brandewie (5):
>> intel_pstate: Set turbo VID for Baytrail
>> intel_pstate: remove setting P state to MAX on init
>> intel_pstate: Fix fixed point rounding macro
>> intel_pstate: Remove C0 tracking
>> intel_pstate: Add CPU IDs for Broadwell processors
>>
>> drivers/cpufreq/intel_pstate.c | 52 +++++++++++++++++-------------------------
>> 1 file changed, 21 insertions(+), 31 deletions(-)
>
> I'll queue them up for 3.15-rc6, but that's a bit too late.
>
> Next time I may just wait for the next merge window, fixes or not.
OK the reporters of the issues already have the fixes in hand.
>
>
prev parent reply other threads:[~2014-05-08 21:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 19:57 [PATCH 0/5] updates for intel_pstate dirk.brandewie
2014-05-08 19:57 ` [PATCH 2/5] intel_pstate: remove setting P state to MAX on init dirk.brandewie
2014-05-08 19:57 ` [PATCH 3/5] intel_pstate: Fix fixed point rounding macro dirk.brandewie
2014-05-12 12:17 ` Rafael J. Wysocki
2014-05-08 19:57 ` [PATCH 4/5] intel_pstate: Remove C0 tracking dirk.brandewie
2014-05-09 1:44 ` Yuyang Du
2014-05-12 0:26 ` Rafael J. Wysocki
[not found] ` <CADmjqpOnzRrB8gJsmHWG=4bvhERLovnKyP0Pcki_uVJ3qpfD0g@mail.gmail.com>
2014-05-12 2:27 ` Stratos Karafotis
2014-05-12 12:16 ` Rafael J. Wysocki
2014-05-12 14:39 ` Dirk Brandewie
2014-05-12 23:45 ` Rafael J. Wysocki
2014-05-08 19:57 ` [PATCH 5/5] intel_pstate: Add CPU IDs for Broadwell processors dirk.brandewie
2014-05-08 20:30 ` [PATCH 0/5] updates for intel_pstate Rafael J. Wysocki
2014-05-08 21:08 ` 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=536BF24E.1000709@gmail.com \
--to=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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).