From: Eduardo Valentin <edubezval@gmail.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Thermal] Need confirmation for the pending thermal soc patches
Date: Mon, 5 Sep 2016 06:16:01 -0700 [thread overview]
Message-ID: <20160905131600.GA24253@localhost.localdomain> (raw)
In-Reply-To: <1471788540.2188.19.camel@intel.com>
Hello Rui,
On Sun, Aug 21, 2016 at 10:09:00PM +0800, Zhang Rui wrote:
> Hi,
>
> As Eduardo is quite busy recently, I will take all the thermal soc
> driver changes this time.
Thanks for helping me out. I am slowing coming back to upstream
activities. I have refreshed my branches, removing the rework and
locking patches works out of the integration branches so we do not have
merge conflicts or further delays on outstanding patches.
> Currently, I have cherry picked all the patches that Eduardo has
> already applied in thermal-soc tree and reviewed all the pending
Great! This makes things easier for me.
> patches in patchwork. Now, there are four patches queued for next -rc (
> https://git.kernel.org/cgit/linux/kernel/git/rzhang/linux.git/log/?h=fo
> r-rc),
I checked this branch. Can you please cherry-pick the following patch
for rc:
https://git.kernel.org/cgit/linux/kernel/git/evalenti/linux-soc-thermal.git/commit/?h=linus&id=4ba16f1256bd13efa2f3179ff1f4ab16a4ad3c7f
?
> and 23 thermal soc patches queued for next merge window (https:/
> /git.kernel.org/cgit/linux/kernel/git/rzhang/linux.git/log/?h=release).
>
> If you think some soc fixes that are urgent and should be in 4.8
> instead of 4.9, please let me know.
> If there are some patches that are neither in thermal -next tree(https:
> //git.kernel.org/cgit/linux/kernel/git/rzhang/linux.git/log/?h=next),
> nor have my response, please let me know, in case I missed some. :)
The above -next branch has all my outstanding material.
Given that you have taken care of all thermal-soc patches for the coming
merging window, I will work on the sysfs rework and locking patches
again. I will be sending them in smaller chunks this time.
>
> thanks,
> rui
next prev parent reply other threads:[~2016-09-05 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 14:09 [Thermal] Need confirmation for the pending thermal soc patches Zhang Rui
2016-09-05 13:16 ` Eduardo Valentin [this message]
2016-09-06 10:13 ` Geert Uytterhoeven
2016-09-07 0:25 ` Zhang Rui
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=20160905131600.GA24253@localhost.localdomain \
--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).