linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Rafael Wysocki <rjw@rjwysocki.net>,
	edubezval@gmail.com
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	dan.carpenter@oracle.com
Subject: Re: [PATCH V2 0/5] thermal: minor cleanup/fixes
Date: Tue, 21 Feb 2017 14:30:27 +0800	[thread overview]
Message-ID: <1487658627.2155.5.camel@intel.com> (raw)
In-Reply-To: <20170220102920.GU21911@vireshk-i7>

On Mon, 2017-02-20 at 15:59 +0530, Viresh Kumar wrote:
> On 07-02-17, 09:39, Viresh Kumar wrote:
> > 
> > Hi,
> > 
> > This series contains minor fixes/cleanups for thermal cooling
> > drivers.
> > 
Acked-by: Zhang Rui <rui.zhang@intel.com>
for the whole patch series.

As this patch set depends on commit 8a31d9d94297 ("PM / OPP: Update OPP
users to put reference"), which goes Rafael' tree, Rafael, can you
please take this patch set as well?

thanks,
rui

  reply	other threads:[~2017-02-21  6:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07  4:09 [PATCH V2 0/5] thermal: minor cleanup/fixes Viresh Kumar
2017-02-07  4:10 ` [PATCH V2 1/5] thermal: devfreq: Simplify expression Viresh Kumar
2017-02-07  4:10 ` [PATCH V2 2/5] thermal: devfreq_cooling: Replace dev_warn with dev_err Viresh Kumar
2017-02-07  4:10 ` [PATCH V2 3/5] thermal: devfreq: Check OPP for errors Viresh Kumar
2017-02-07  4:10 ` [PATCH V2 4/5] thermal: cpu_cooling: Replace dev_warn with dev_err Viresh Kumar
2017-02-07  4:10 ` [PATCH V2 5/5] thermal: cpu_cooling: Check OPP for errors Viresh Kumar
2017-02-20 10:29 ` [PATCH V2 0/5] thermal: minor cleanup/fixes Viresh Kumar
2017-02-21  6:30   ` Zhang Rui [this message]
2017-02-24  8:49     ` Viresh Kumar
2017-03-08  4:24       ` Viresh Kumar

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=1487658627.2155.5.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=dan.carpenter@oracle.com \
    --cc=edubezval@gmail.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.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).