All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Wei Ni <wni@nvidia.com>
Cc: rui.zhang@intel.com, thierry.reding@gmail.com,
	MLongnecker@nvidia.com, swarren@wwwdotorg.org,
	mikko.perttunen@kapsi.fi, linux-tegra@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V7 08/12] of: add notes of critical trips for soctherm
Date: Mon, 14 Mar 2016 14:00:28 -0700	[thread overview]
Message-ID: <20160314210027.GA4740@localhost.localdomain> (raw)
In-Reply-To: <1457665860-30003-1-git-send-email-wni@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 523 bytes --]

On Fri, Mar 11, 2016 at 11:11:00AM +0800, Wei Ni wrote:
> The "critical" type trip in thermal zone can be
> set to SOC_THERM hardware, it can trigger shut down
> or reset event from hardware.
> 
> Signed-off-by: Wei Ni <wni@nvidia.com>
> Acked-by: Rob Herring <robh@kernel.org>
> ---
>  Documentation/devicetree/bindings/thermal/tegra-soctherm.txt | 12 ++++++++++++
>  1 file changed, 12 insertions(+)

I did not see in your patch set an update on the compatible string for
the new chip. Did I miss something?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-03-14 21:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11  3:11 [PATCH V7 08/12] of: add notes of critical trips for soctherm Wei Ni
2016-03-11  3:11 ` Wei Ni
2016-03-14 21:00 ` Eduardo Valentin [this message]
     [not found]   ` <20160314210027.GA4740-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2016-03-15  7:49     ` Wei Ni
2016-03-15  7:49       ` Wei Ni
2016-03-15  8:14       ` Wei Ni
2016-03-15  8:14         ` Wei Ni
     [not found]         ` <56E7C457.5000301-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-03-15 19:52           ` Eduardo Valentin
2016-03-15 19:52             ` Eduardo Valentin

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=20160314210027.GA4740@localhost.localdomain \
    --to=edubezval@gmail.com \
    --cc=MLongnecker@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mikko.perttunen@kapsi.fi \
    --cc=rui.zhang@intel.com \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.com \
    --cc=wni@nvidia.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.