From: Caesar Wang <wxt@rock-chips.com>
To: edubezval@gmail.com, rui.zhang@intel.com
Cc: linux-rockchip@lists.infradead.org, linux-pm@vger.kernel.org,
briannorris@chromium.org, linux-kernel@vger.kernel.org,
smbarber@chromium.org, Caesar Wang <wxt@rock-chips.com>
Subject: [PATCH v2 0/5] thermal: fixes the rockchip thermal
Date: Wed, 23 Nov 2016 22:29:29 +0800 [thread overview]
Message-ID: <1479911374-22006-1-git-send-email-wxt@rock-chips.com> (raw)
There are five patches posted for upstream.
89267b5 thermal: rockchip: improve conversion error messages
a0b5649 thermal: rockchip: don't pass table structs by value
bceed92 thermal: rockchip: fixes invalid temperature case
30be6d0 thermal: rockchip: optimize the conversion table
35636e9 thermal: rockchip: handle the set_trips without the trip points.
--
Brain posted the below patches for upstream.
89267b5 thermal: rockchip: improve conversion error messages
a0b5649 thermal: rockchip: don't pass table structs by value
That make sense to improve efficiency
Caesar post the below patches for upstream.
bceed92 thermal: rockchip: fixes invalid temperature case
30be6d0 thermal: rockchip: optimize the conversion table
35636e9 thermal: rockchip: handle the set_trips without the trip points.
That will fixes some issue in special cases.
--
Anyway, this series patches should can improve the rockchip thermal driver.
Changes in v2:
- As Brian commnets that restructure this to pass error codes back to the
upper layers.
- Improve the commit message.
- improve the commit as Brian commnets on https://patchwork.kernel.org/patch/9440985
- Fixes something as Brian comments on
https://patchwork.kernel.org/patch/9440989.
Changes in v1:
- The original Brian posted on https://patchwork.kernel.org/patch/9437686
Note: it'd probably be even nicer to know which sensor this was, but we've
kinda abstracted that one away by this point...
- The original Brian posted on https://patchwork.kernel.org/patch/9437687
Brian Norris (2):
thermal: rockchip: improve conversion error messages
thermal: rockchip: don't pass table structs by value
Caesar Wang (3):
thermal: rockchip: fixes invalid temperature case
thermal: rockchip: optimize the conversion table
thermal: rockchip: handle set_trips without the trip points
drivers/thermal/rockchip_thermal.c | 147 +++++++++++++++++++++++++------------
1 file changed, 101 insertions(+), 46 deletions(-)
--
2.7.4
next reply other threads:[~2016-11-23 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 14:29 Caesar Wang [this message]
2016-11-23 14:29 ` [PATCH v2 1/5] thermal: rockchip: improve conversion error messages Caesar Wang
2016-11-23 14:29 ` [PATCH v2 2/5] thermal: rockchip: don't pass table structs by value Caesar Wang
2016-11-23 14:29 ` [PATCH v2 3/5] thermal: rockchip: fixes invalid temperature case Caesar Wang
2016-11-23 18:35 ` Brian Norris
2016-11-24 1:16 ` Caesar Wang
2016-11-23 14:29 ` [PATCH v2 4/5] thermal: rockchip: optimize the conversion table Caesar Wang
2016-11-23 14:29 ` [PATCH v2 5/5] thermal: rockchip: handle set_trips without the trip points Caesar Wang
2016-11-23 18:39 ` Brian Norris
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=1479911374-22006-1-git-send-email-wxt@rock-chips.com \
--to=wxt@rock-chips.com \
--cc=briannorris@chromium.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=rui.zhang@intel.com \
--cc=smbarber@chromium.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
Powered by JetHome