public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: Rui Zhang <rui.zhang@intel.com>,
	Linux PM <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Samsung Thermal fixes for v4.0-rc2
Date: Tue, 03 Mar 2015 09:01:58 +0100	[thread overview]
Message-ID: <20150303090158.509eda55@amdc2363> (raw)
In-Reply-To: <20150303022117.GA14070@developer.hsd1.ca.comcast.net>

Hi Eduardo,

> On Mon, Mar 02, 2015 at 11:43:47AM +0100, Lukasz Majewski wrote:
> > Dear Eduardo,
> > 
> > Please find my first pull request for Samsung Thermal fixes
> > targeting v4.0-rc2.
> > 
> 
> Pulled. Thanks. 
> 
> Couple of minor comments though (check next on your pull)

I'm fully aware that I might have made some mistakes, since this is my
first PR :-)

Thanks for comments.

> 
> > Changes:
> > - Exynos7 power down detection mode fix
> > - Fix for cpufreq cooling device regression
> > - Updating MAINTAINER's entry for Samsung Exynos Thermal 
> > 
> > 
> > 
> > The following changes since commit
> > 5912e264d9eec512598d8faf33440630a3aee989:
> > 
> >   Merge branch 'tmon-fixes' of .git into next (2015-02-28 14:07:03
> >   +0800)
> > 
> > are available in the git repository at:
> > 
> > 
> >   git@github.com:lmajewski/linux-samsung-thermal.git
> >   github_linux-samusng-thermal/fixes
> 
> This branch does not really exist. But I figure you want to mention
> 'fixes' branch.
> 
> > 
> > for you to fetch changes up to
> > 93c537affd5d2a7b2fcea4a1d608b011841d3c04:
> > 
> >   MAINTAINERS: Add entry for SAMSUNG THERMAL DRIVER (2015-03-02
> >   10:06:09 +0100)
> > 
> > ----------------------------------------------------------------
> > Chanwoo Choi (1):
> >       thermal: exynos: Fix wrong control of power down detection
> > mode for Exynos7
> > 
> > Lukasz Majewski (2):
> >       cpufreq: exynos: Use simple approach to asses if cpu cooling
> > can be used MAINTAINERS: Add entry for SAMSUNG THERMAL DRIVER
> > 
> >  MAINTAINERS                          |  8 ++++++++
> >  drivers/cpufreq/exynos-cpufreq.c     | 21 ++++++---------------
> 
> As this one was a left over and was acked by cpufreq maintainer, I am
> picking this time. But even in the case of an ack, I would really
> prefer to have each change going via their respective tree whenever
> possible.
> 
> >  drivers/thermal/samsung/exynos_tmu.c |  3 ++-
> >  3 files changed, 16 insertions(+), 16 deletions(-)
> > 
> > 
> > -- 
> > Best regards,
> > 
> > Lukasz Majewski
> > 
> > Samsung R&D Institute Poland (SRPOL) | Linux Platform Group

-- 
Best regards,

Lukasz Majewski

Samsung R&D Institute Poland (SRPOL) | Linux Platform Group

      reply	other threads:[~2015-03-03  8:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 10:43 [GIT PULL] Samsung Thermal fixes for v4.0-rc2 Lukasz Majewski
2015-03-03  2:21 ` Eduardo Valentin
2015-03-03  8:01   ` Lukasz Majewski [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=20150303090158.509eda55@amdc2363 \
    --to=l.majewski@samsung.com \
    --cc=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