linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Thermal management updates for v4.11-rc5
Date: Thu, 30 Mar 2017 10:50:09 +0800	[thread overview]
Message-ID: <1490842209.2347.9.camel@intel.com> (raw)

Hi, Linus,

Please pull from
  git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git for-rc

to receive the latest Thermal Management updates for v4.11-rc5 with
top-most commit 3ea3217cf91804be6ed9b368ef4ac7911eb1dadc:

  thermal: cpu_cooling: Check OPP for errors (2017-03-13 10:06:55
+0800)

on top of commit 4495c08e84729385774601b5146d51d9e5849f81:

  Linux 4.11-rc2 (2017-03-12 14:47:08 -0700)

Specifics:

- Fix a potential deadlock in cpu_cooling driver, which was introduced
in 4.11-rc1. (Matthew Wilcox)

- Fix the cpu_cooling and devfreq_cooling code to handle possible error
return value from OPP calls, together with three minor fixes in the
same patch series. (Viresh Kumar)

thanks,
rui

----------------------------------------------------------------
Matthew Wilcox (1):
      thermal: Fix potential deadlock in cpu_cooling

Viresh Kumar (5):
      thermal: devfreq: Simplify expression
      thermal: devfreq_cooling: Replace dev_warn with dev_err
      thermal: devfreq: Check OPP for errors
      thermal: cpu_cooling: Replace dev_warn with dev_err
      thermal: cpu_cooling: Check OPP for errors

 drivers/thermal/cpu_cooling.c     | 39 ++++++++++++++++++++++++-------
--------
 drivers/thermal/devfreq_cooling.c | 14 ++++++++++----
 2 files changed, 34 insertions(+), 19 deletions(-)

                 reply	other threads:[~2017-03-30  2:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1490842209.2347.9.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).