From: Brian Norris <briannorris@chromium.org>
To: Caesar Wang <wxt@rock-chips.com>
Cc: edubezval@gmail.com, rui.zhang@intel.com,
linux-rockchip@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, smbarber@chromium.org
Subject: Re: [PATCH v2 5/5] thermal: rockchip: handle set_trips without the trip points
Date: Wed, 23 Nov 2016 10:39:53 -0800 [thread overview]
Message-ID: <20161123183953.GB12380@google.com> (raw)
In-Reply-To: <1479911374-22006-6-git-send-email-wxt@rock-chips.com>
On Wed, Nov 23, 2016 at 10:29:34PM +0800, Caesar Wang wrote:
> In some cases, some sensors didn't need the trip points, the
> set_trips will return {-INT_MAX, INT_MAX} to trigger thermal alarm.
>
> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
> ---
>
> Changes in v2:
> - Fixes something as Brian comments on
> https://patchwork.kernel.org/patch/9440989.
>
> Changes in v1: None
I think this looks better.
Reviewed-by: Brian Norris <briannorris@chromium.org>
prev parent reply other threads:[~2016-11-23 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 14:29 [PATCH v2 0/5] thermal: fixes the rockchip thermal Caesar Wang
2016-11-23 14:29 ` Caesar Wang
2016-11-23 14:29 ` [PATCH v2 2/5] thermal: rockchip: don't pass table structs by value Caesar Wang
[not found] ` <1479911374-22006-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-11-23 14:29 ` [PATCH v2 1/5] thermal: rockchip: improve conversion error messages Caesar Wang
2016-11-23 14:29 ` Caesar Wang
2016-11-23 14:29 ` [PATCH v2 3/5] thermal: rockchip: fixes invalid temperature case Caesar Wang
2016-11-23 14:29 ` 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 ` 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 14:29 ` Caesar Wang
2016-11-23 18:39 ` Brian Norris [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=20161123183953.GB12380@google.com \
--to=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 \
--cc=wxt@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.