From: Eduardo Valentin <edubezval@gmail.com>
To: Rui Zhang <rui.zhang@intel.com>
Cc: Linux PM <linux-pm@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] thermal-soc updates for v3.18-rc7
Date: Mon, 24 Nov 2014 17:25:08 -0400 [thread overview]
Message-ID: <20141124212506.GA1685@developer> (raw)
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
Hello Rui,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal.git fixes
to receive thermal-soc updates for v3.18-rc7 with top-most
d3e19567fa85e1a0dab02205b89b2908084ecadd:
thermal: Exynos: Deletion of unnecessary checks before two function calls (2014-11-21 15:20:17 -0400)
on top of commit fc14f9c1272f62c3e8d01300f52467c0d9af50f9:
Linux 3.18-rc5 (2014-11-16 16:36:20 -0800)
Specifics:
In this -rc still very minor changes:
- Lee Jones fixes compilation warning in sti thermal driver;
- Marjus Elfring removes unnecessary checks in exynos thermal driver
(as per coccinelle); and
- Now we always update cpufreq policies, and thus get (hopefully) always in sync with cpufreq,
thanks to Yadwinder.
BR,
Eduardo Valentin
----------------------------------------------------------------
Lee Jones (1):
thermal: sti: Ignore suspend/resume functions when !PM_SLEEP
Markus Elfring (1):
thermal: Exynos: Deletion of unnecessary checks before two function calls
Yadwinder Singh Brar (1):
thermal: cpu_cooling: Update always cpufreq policy with thermal constraints
drivers/thermal/cpu_cooling.c | 37 ++++++++++++++-----------
drivers/thermal/samsung/exynos_thermal_common.c | 9 ++----
drivers/thermal/st/st_thermal.c | 3 ++
3 files changed, 27 insertions(+), 22 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2014-11-24 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 21:25 Eduardo Valentin [this message]
2014-11-26 15:27 ` [GIT PULL] thermal-soc updates for v3.18-rc7 Eduardo Valentin
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=20141124212506.GA1685@developer \
--to=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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).