All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Sebastien Rannou <mxs@sbrk.org>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [GIT PULL] cpuidle: 4.0-rc3 fixes
Date: Fri, 13 Mar 2015 22:56:59 +0100	[thread overview]
Message-ID: <2429393.iDkfxR0R07@vostro.rjw.lan> (raw)
In-Reply-To: <55032186.3000306@linaro.org>

On Friday, March 13, 2015 06:42:30 PM Daniel Lezcano wrote:
> 
> Hi Rafael,
> 
> this pull request contains a couple of fixes:
> 
>   - Fix the cpu_pm_enter/exit symmetry in the mvebu driver (Gregory Clement)
> 
>   - Fix the mvebu drivers latency/residency values to reach an 
> acceptable tradeoff between perf / power (Sebastian Rannou)
> 
> Thanks !

Pulled, but this is a bit too late for 4.0-rc4, so I'll queue it up for -rc5.

> ps: I took the opportunity to double check the other drivers have their 
> cpu_pm_entry/exit symmetry correct (everything ok).

OK, thanks!

BTW, please update the dead linux-pm address you have in your scripts.


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

  parent reply	other threads:[~2015-03-13 21:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 17:42 [GIT PULL] cpuidle: 4.0-rc3 fixes Daniel Lezcano
2015-03-13 17:43 ` [PATCH 1/2] cpuidle: mvebu: Fix the CPU PM notifier usage Daniel Lezcano
2015-03-13 17:43   ` [PATCH 2/2] cpuidle: mvebu: Update cpuidle thresholds for Armada XP SOCs Daniel Lezcano
2015-03-13 21:56 ` Rafael J. Wysocki [this message]
2015-03-13 21:38   ` [GIT PULL] cpuidle: 4.0-rc3 fixes Daniel Lezcano
2015-03-16  9:24   ` Geert Uytterhoeven
2015-03-17  2:37     ` Rafael J. Wysocki
2015-03-17  6:53       ` Geert Uytterhoeven

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=2429393.iDkfxR0R07@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mxs@sbrk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.