mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: dirk.brandewie@gmail.com
Cc: linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 0/6] Intel pstate driver update
Date: Wed, 08 May 2013 02:07:15 +0200	[thread overview]
Message-ID: <4686510.A1KmKYg1tS@vostro.rjw.lan> (raw)
In-Reply-To: <1367940030-19311-1-git-send-email-dirk.j.brandewie@gmail.com>

On Tuesday, May 07, 2013 08:20:24 AM dirk.brandewie@gmail.com wrote:
> From: dirk <dirk.brandewie@gmail.com>
> 
> Collection of updates for cpufreq/intel_pstate.c
> 
> Patches 1-3 are bugfixes and marked for stable
> 
> Patches 4-6 are code cleanup with no functional changes.
> 
> 
> Dirk Brandewie (6):
>   cpufreq/intel_pstate: remove idle time and duration from sample and
>     calculations
>   cpufreq/intel_pstate: use lowest requested max performance
>   cpufreq/intel_pstate: fix ffmpeg regression
>   cpufreq/intel_pstate: Remove idle mode PID
>   cpufreq/intel_pstate: Remove unused code
>   cpufreq/intel_pstate: remove #ifdef MODULE compile fence
> 
>  drivers/cpufreq/intel_pstate.c | 122 +++++++----------------------------------
>  1 file changed, 20 insertions(+), 102 deletions(-)

All queued up for a post-3.10-rc1 push as 3.10 material, but I have a couple
of comments.

First, the patches didn't apply for me cleanly.  I needed to fix up one of
them manually to make it apply and patch [5/6] didn't appear to be necessary
at all (it made changes that had been made previously).  Please check the
bleeding-edge branch of my tree to see if the code is what you wanted and
let me know (either way).

Second, can you please CC your cpufreq submissions to linux-pm@vger.kernel.org?
That will allow me to use Patchwork for managing them, which is much more
convenient than plain email.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  parent reply	other threads:[~2013-05-07 23:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 15:20 dirk.brandewie
2013-05-07 15:20 ` [PATCH 1/6] cpufreq/intel_pstate: remove idle time and duration from sample and calculations dirk.brandewie
2013-05-07 15:20 ` [PATCH 2/6] cpufreq/intel_pstate: use lowest requested max performance dirk.brandewie
2013-05-07 15:20 ` [PATCH 3/6] cpufreq/intel_pstate: fix ffmpeg regression dirk.brandewie
2013-05-07 15:20 ` [PATCH 4/6] cpufreq/intel_pstate: Remove idle mode PID dirk.brandewie
2013-05-07 15:20 ` [PATCH 5/6] cpufreq/intel_pstate: Remove unused code dirk.brandewie
2013-05-07 15:20 ` [PATCH 6/6] cpufreq/intel_pstate: remove #ifdef MODULE compile fence dirk.brandewie
2013-05-08  0:07 ` Rafael J. Wysocki [this message]
2013-05-08  0:21   ` [PATCH 0/6] Intel pstate driver update Dirk Brandewie
2013-05-08 11:56     ` 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=4686510.A1KmKYg1tS@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=dirk.brandewie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    /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®