From: Eduardo Valentin <edubezval@gmail.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Wei Ni <wni@nvidia.com>,
thierry.reding@gmail.com, daniel.lezcano@linaro.org,
linux-tegra@vger.kernel.org, srikars@nvidia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/4] Fixes for Tegra soctherm
Date: Tue, 18 Dec 2018 13:31:28 -0800 [thread overview]
Message-ID: <20181218213126.GA8850@localhost.localdomain> (raw)
In-Reply-To: <1545104154.2052.2.camel@intel.com>
On Tue, Dec 18, 2018 at 11:35:54AM +0800, Zhang Rui wrote:
> On 五, 2018-12-14 at 17:54 +0800, Wei Ni wrote:
> > Hi Rui,
> > I moved get_trend() patch https://lkml.org/lkml/2018/11/20/643 in
> > this
> > serial.
> > Since no more comments on these patches, will you take them?
> >
> I think Eduardo will take care of this patch series.
Yes, I will take a look on this series.
But, please, next time you send a series of patches on thermal, copy the
linux-pm@vger.kernel.org mailing list. This way we can track your
patches on patchwork.
>
> thanks,
> rui
> > Thanks.
> > Wei.
> >
> > On 14/12/2018 5:49 PM, Wei Ni wrote:
> > >
> > > This series fixed some issues for Tegra soctherm,
> > > and add get_trend().
> > >
> > > Main changes from v5:
> > > 1. Move the get_trend() patch https://lkml.org/lkml/2018/11/20/643
> > > into this serial.
> > >
> > > 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 (4):
> > > thermal: tegra: remove unnecessary warnings
> > > thermal: tegra: fix memory allocation
> > > thermal: tegra: parse sensor id before sensor register
> > > thermal: tegra: add get_trend ops
> > >
> > > drivers/thermal/tegra/soctherm.c | 85
> > > +++++++++++++++++++++++++++++++++++++---
> > > 1 file changed, 80 insertions(+), 5 deletions(-)
> > >
next prev parent reply other threads:[~2018-12-18 21:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 9:49 [PATCH v6 0/4] Fixes for Tegra soctherm Wei Ni
2018-12-14 9:49 ` [PATCH v6 1/4] thermal: tegra: remove unnecessary warnings Wei Ni
2018-12-14 14:18 ` Thierry Reding
2018-12-14 9:49 ` [PATCH v6 2/4] thermal: tegra: fix memory allocation Wei Ni
2018-12-14 9:49 ` [PATCH v6 3/4] thermal: tegra: parse sensor id before sensor register Wei Ni
2018-12-14 14:19 ` Thierry Reding
2018-12-19 1:24 ` Eduardo Valentin
2018-12-19 3:00 ` Wei Ni
2018-12-19 14:57 ` Eduardo Valentin
2018-12-20 2:44 ` Wei Ni
2018-12-14 9:49 ` [PATCH v6 4/4] thermal: tegra: add get_trend ops Wei Ni
2018-12-14 14:19 ` Thierry Reding
2018-12-14 9:54 ` [PATCH v6 0/4] Fixes for Tegra soctherm Wei Ni
2018-12-18 3:35 ` Zhang Rui
2018-12-18 21:31 ` Eduardo Valentin [this message]
2018-12-19 3:14 ` 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=20181218213126.GA8850@localhost.localdomain \
--to=edubezval@gmail.com \
--cc=daniel.lezcano@linaro.org \
--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 \
--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;
as well as URLs for NNTP newsgroup(s).