linux-kernel.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.8-rc4
Date: Thu, 25 Aug 2016 15:58:50 +0800	[thread overview]
Message-ID: <1472111930.2167.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.8-rc4 with
top-most commit 829bc78aa7628e81a9de717316b85cbee3c5eb86:

  thermal: imx: fix a possible NULL dereference (2016-08-19 21:34:08
+0800)

on top of commit 694d0d0bb2030d2e36df73e2d23d5770511dbc8d:

  Linux 4.8-rc2 (2016-08-14 19:11:36 -0700)

Specifics:
- Fix cpu_cooling to have separate thermal_cooling_device_ops
structures for cpus with and without power model, to avoid NULL
dereference in cpufreq_state2power. From Brendan Jackman.
- Fix a possible NULL dereference in imx_thermal driver. From Corentin
LABBE .
- Another two trivial fixes, one typo fix and one deleting module
owner. From Caesar Wang and Markus Elfring.

thanks,
rui

----------------------------------------------------------------
Brendan Jackman (1):
      thermal: cpu_cooling: Fix NULL dereference in cpufreq_state2power

Caesar Wang (1):
      thermal: trivial: fix the typo

Corentin LABBE (1):
      thermal: imx: fix a possible NULL dereference

Markus Elfring (1):
      Thermal-INT3406: Delete owner assignment

 .../devicetree/bindings/thermal/thermal.txt         | 10 +++++-----
 drivers/thermal/cpu_cooling.c                       | 21
++++++++++++++++-----
 drivers/thermal/imx_thermal.c                       |  4 +---
 drivers/thermal/int340x_thermal/int3406_thermal.c   |  1 -
 4 files changed, 22 insertions(+), 14 deletions(-)

                 reply	other threads:[~2016-08-25  7:59 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=1472111930.2167.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).