From: caesar.upstream@gmail.com (Caesar Wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/5] Thermal: Support for hardware-tracked trip points
Date: Wed, 22 Jun 2016 19:19:24 +0800 [thread overview]
Message-ID: <576A743C.7080401@gmail.com> (raw)
In-Reply-To: <1466565939.2379.5.camel@intel.com>
On 2016?06?22? 11:25, Zhang Rui wrote:
> On ?, 2016-06-21 at 09:42 +0800, Caesar Wang wrote:
>> Do you have other ideas for the following patches? :-)
>> Even if only took two weeks feel after a long time.
>>
>> 9157919 New [v5,1/5] thermal: Add support for hardware-
>> tracked trip points
>> 9157917 New [v5,2/5] thermal: of: implement .set_trips for
>> device tree thermal zones
>> 9161129 New [v5.1,3/5] thermal: streamline get_trend
>> callbacks
>> 9157929 New [v5,4/5] thermal: bang-bang governor: act on
>> lower trip boundary
>> 9157925 New [v5,5/5] thermal: rockchip: add the set_trips
>> function
>> ---
>>
> I have no objections to this patch set, except one change in patch 1/5.
> But as this also touches of_thermal and rockchip thermal driver. I'd
> leave this patch set for Eduardo to review and take.
> BTW, Eduardo is traveling recently, so you may still need to wait some
> time.
Okay, thanks for your reminder. and sorry for the noise.:-)
-
Caesar
>
> Thanks,
> rui
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2016-06-22 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 11:44 [PATCH v5 0/5] Thermal: Support for hardware-tracked trip points Caesar Wang
2016-06-06 11:44 ` [PATCH v5 5/5] thermal: rockchip: add the set_trips function Caesar Wang
[not found] ` <57689B82.3000902@gmail.com>
2016-06-22 3:25 ` [PATCH v5 0/5] Thermal: Support for hardware-tracked trip points Zhang Rui
2016-06-22 11:19 ` Caesar Wang [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=576A743C.7080401@gmail.com \
--to=caesar.upstream@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).