From: Eduardo Valentin <edubezval@gmail.com>
To: Wei Ni <wni@nvidia.com>
Cc: thierry.reding@gmail.com, robh+dt@kernel.org,
rui.zhang@intel.com, MLongnecker@nvidia.com,
swarren@wwwdotorg.org, mikko.perttunen@kapsi.fi,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/9] thermal: tegra: add Tegra132 specific SOC_THERM driver
Date: Wed, 27 Apr 2016 16:39:22 -0700 [thread overview]
Message-ID: <20160427233921.GA2590@localhost.localdomain> (raw)
In-Reply-To: <1461727554-15065-2-git-send-email-wni@nvidia.com>
On Wed, Apr 27, 2016 at 11:25:46AM +0800, Wei Ni wrote:
> add Tegra132 specific SOC_THERM driver.
Applied this one. You may also add my
Acked-by: Eduardo Valentin <edubezval@gmail.com>
for patches 2 and 3. Remaining of the patches need to be further
discussed.
>
> Signed-off-by: Wei Ni <wni@nvidia.com>
next prev parent reply other threads:[~2016-04-27 23:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 3:25 [PATCH v2 0/9] Add HW throttle for Tegra soctherm Wei Ni
2016-04-27 3:25 ` [PATCH v2 1/9] thermal: tegra: add Tegra132 specific SOC_THERM driver Wei Ni
2016-04-27 23:39 ` Eduardo Valentin [this message]
2016-04-27 3:25 ` [PATCH v2 2/9] arm64: tegra: use tegra132-soctherm for Tegra132 Wei Ni
2016-04-27 3:25 ` [PATCH v2 3/9] arm64: tegra: set critical trips " Wei Ni
2016-04-27 3:25 ` [PATCH v2 4/9] of: Add bindings of hw throttle for soctherm Wei Ni
2016-04-27 23:30 ` Eduardo Valentin
2016-04-28 6:48 ` Wei Ni
2016-04-28 14:48 ` Eduardo Valentin
2016-04-29 5:55 ` Wei Ni
2016-04-27 3:25 ` [PATCH v2 5/9] thermal: tegra: add hw-throttle function Wei Ni
2016-04-27 3:25 ` [PATCH v2 6/9] thermal: tegra: add hw-throttle for Tegra132 Wei Ni
2016-04-27 3:25 ` [PATCH v2 7/9] arm64: tegra: set hot trips for Tegra210 Wei Ni
2016-04-27 3:25 ` [PATCH v2 8/9] arm64: tegra: set hot trips for Tegra132 Wei Ni
2016-04-27 3:25 ` [PATCH v2 9/9] arm: tegra: set hot trips for Tegra124 Wei Ni
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=20160427233921.GA2590@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=MLongnecker@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mikko.perttunen@kapsi.fi \
--cc=robh+dt@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox