From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>, Zhang Rui <rui.zhang@intel.com>
Cc: edubezval@gmail.com, 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: Wed, 8 Mar 2017 09:54:20 +0530 [thread overview]
Message-ID: <20170308042420.GC4526@vireshk-i7> (raw)
In-Reply-To: <20170224084936.GB7147@vireshk-i7>
On 24-02-17, 14:19, Viresh Kumar wrote:
> On 21-02-17, 14:30, Zhang Rui wrote:
> > 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?
>
> @Rafael: Can you please apply these as well ?
Ping !!
--
viresh
prev parent reply other threads:[~2017-03-08 4:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 4:09 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
2017-02-24 8:49 ` Viresh Kumar
2017-03-08 4:24 ` Viresh Kumar [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=20170308042420.GC4526@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--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=rui.zhang@intel.com \
--cc=vincent.guittot@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
all inboxes | Powered by JetHome®