linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <eduardo.valentin@ti.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Eduardo Valentin <eduardo.valentin@ti.com>,
	amit.daniel@samsung.com, l.majewski@samsung.com,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [GIT PULL] thermal-soc: urgent fixes for 3.12
Date: Tue, 15 Oct 2013 10:09:07 -0400	[thread overview]
Message-ID: <525D4C83.706@ti.com> (raw)
In-Reply-To: <1381837008.2080.61.camel@rzhang1-mobl4>

[-- Attachment #1: Type: text/plain, Size: 2333 bytes --]

On 15-10-2013 07:36, Zhang Rui wrote:
> Hi, Eduardo,
> 
> On Mon, 2013-10-14 at 18:00 -0400, Eduardo Valentin wrote:
>> Hello Rui,
>>
>> Please pull the following changes. It contains fixes for 3.12 on Exynos
>> thermal driver, which is currently broken, Exynos4412 is the main affected.
>> Thanks Lukasz for his persistence on getting this done for 3.12.
>>
>> Lukasz, you need to queue the remaining changes on DT via your platform tree.
>>
>> It contains also a fix on the extrapolation rules for TI SoCs.
>>
>> The following changes since commit 74ae45a3d656d3e86bb8e776634ebdfd3f39f37c:
>>
>>   Merge branches 'x86_pkg_temp' and 'misc' of .git into next (2013-09-25 21:41:44 +0800)
>>
> please rebase your tree on top of my master branch or Linus' tree.
> Or else I'll pull in some thermal changes in my next branch that are
> targeted for 3.13.

In fact, my bad. I am rebasing on top of your master and resending.

> 
> thanks,
> rui
>> are available in the git repository at:
>>
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal.git next
>>
>> for you to fetch changes up to 848a3b2b91a45f6b7814e2779f58cc0461d88fce:
>>
>>   drivers: thermal: allow ti-soc-thermal run without pcb zone (2013-10-14 17:48:33 -0400)
>>
>> ----------------------------------------------------------------
>> Eduardo Valentin (1):
>>       drivers: thermal: allow ti-soc-thermal run without pcb zone
>>
>> Lukasz Majewski (3):
>>       thermal: exynos: Remove check for thermal device pointer at exynos_report_trigger()
>>       thermal: exynos: Provide separate TMU data for Exynos4412
>>       thermal: exynos: Provide initial setting for TMU's test MUX address at Exynos4412
>>
>>  drivers/thermal/samsung/exynos_thermal_common.c    |  2 --
>>  drivers/thermal/samsung/exynos_tmu.c               | 12 ++++++---
>>  drivers/thermal/samsung/exynos_tmu.h               |  7 ++++-
>>  drivers/thermal/samsung/exynos_tmu_data.c          | 30 +++++++++++++++++-----
>>  drivers/thermal/samsung/exynos_tmu_data.h          | 13 +++++++++-
>>  drivers/thermal/ti-soc-thermal/ti-thermal-common.c |  1 +
>>  6 files changed, 51 insertions(+), 14 deletions(-)
> 
> 
> 
> 


-- 
You have got to be excited about what you are doing. (L. Lamport)

Eduardo Valentin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 bytes --]

      reply	other threads:[~2013-10-15 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 22:00 [GIT PULL] thermal-soc: urgent fixes for 3.12 Eduardo Valentin
2013-10-15 11:36 ` Zhang Rui
2013-10-15 14:09   ` Eduardo Valentin [this message]

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=525D4C83.706@ti.com \
    --to=eduardo.valentin@ti.com \
    --cc=amit.daniel@samsung.com \
    --cc=l.majewski@samsung.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).