From: Wei Ni <wni@nvidia.com>
To: <thierry.reding@gmail.com>, <daniel.lezcano@linaro.org>,
<linux-tegra@vger.kernel.org>
Cc: <rui.zhang@intel.com>, <edubezval@gmail.com>,
<srikars@nvidia.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] Fixes for Tegra soctherm
Date: Wed, 5 Dec 2018 16:31:26 +0800 [thread overview]
Message-ID: <56fd1fc8-f70f-2d86-6a05-799a7bd0ff7e@nvidia.com> (raw)
In-Reply-To: <1543816523-10525-1-git-send-email-wni@nvidia.com>
Hi,
Does there have any comments on this serial?
Thanks.
Wei.
On 3/12/2018 1:55 PM, Wei Ni wrote:
> This series fixed some issues for Tegra soctherm
>
> Main changes from v4:
> 1. fixed for the parsing sensor id.
> 2. keep warning for missing critical trips.
>
> Main changes from v3:
> 1. updated codes for parsing sensor id, per Thierry's comments
>
> Main changes from v2:
> 1. add codes to parse sensor id to avoid registration
> failure.
>
> Main changes from v1:
> 1. Acked by Thierry Reding <treding@nvidia.com> for the patch
> "thermal: tegra: fix memory allocation".
> 2. Print out the sensor name when register failed.
> 2. Remove patch "thermal: tegra: fix coverity defect"
>
> Wei Ni (3):
> thermal: tegra: remove unnecessary warnings
> thermal: tegra: fix memory allocation
> thermal: tegra: parse sensor id before sensor register
>
> drivers/thermal/tegra/soctherm.c | 51 ++++++++++++++++++++++++++++++++++++----
> 1 file changed, 46 insertions(+), 5 deletions(-)
>
next prev parent reply other threads:[~2018-12-05 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 5:55 Wei Ni
2018-12-03 5:55 ` [PATCH v5 1/3] thermal: tegra: remove unnecessary warnings Wei Ni
2018-12-03 5:55 ` [PATCH v5 2/3] thermal: tegra: fix memory allocation Wei Ni
2018-12-03 5:55 ` [PATCH v5 3/3] thermal: tegra: parse sensor id before sensor register Wei Ni
2018-12-05 8:31 ` Wei Ni [this message]
2018-12-11 5:54 ` [PATCH v5 0/3] Fixes for Tegra soctherm 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=56fd1fc8-f70f-2d86-6a05-799a7bd0ff7e@nvidia.com \
--to=wni@nvidia.com \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=srikars@nvidia.com \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®