From: Zhang Rui <rui.zhang@intel.com>
To: Wei Ni <wni@nvidia.com>, daniel.lezcano@linaro.org, edubezval@gmail.com
Cc: thierry.reding@gmail.com, linux-tegra@vger.kernel.org,
srikars@nvidia.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v7 0/3] Fixes for Tegra soctherm
Date: Wed, 20 Feb 2019 10:14:01 +0800 [thread overview]
Message-ID: <1550628841.3372.1.camel@intel.com> (raw)
In-Reply-To: <df2493f3-4bbd-65d1-1205-073a30729a89@nvidia.com>
On 一, 2019-02-18 at 15:59 +0800, Wei Ni wrote:
> Rui,
> Will you take this serial?
>
it is already in my tree.
I missed -rc6, thus I will queue them for 5.1-rc1.
thanks,
rui
> Thanks.
> Wei.
>
> On 21/1/2019 5:17 PM, Wei Ni wrote:
> >
> > Does there have any comments?
> >
> > Thanks.
> > Wei.
> >
> > On 11/1/2019 10:20 AM, Wei Ni wrote:
> > >
> > > Hi Eduardo,
> > > Do you have any more comments, will you take this serial?
> > >
> > > Thanks.
> > > Wei.
> > >
> > > On 3/1/2019 6:12 PM, Wei Ni wrote:
> > > >
> > > > This series fixed some issues for Tegra soctherm,
> > > > and add get_trend().
> > > >
> > > > Main changes from v6:
> > > > 1. Per Eduardo's comment, we can remove the change:
> > > > "thermal: tegra: parse sensor id before sensor register"
> > > >
> > > > 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 (3):
> > > > thermal: tegra: remove unnecessary warnings
> > > > thermal: tegra: fix memory allocation
> > > > thermal: tegra: add get_trend ops
> > > >
> > > > drivers/thermal/tegra/soctherm.c | 40
> > > > +++++++++++++++++++++++++++++++++++++---
> > > > 1 file changed, 37 insertions(+), 3 deletions(-)
> > > >
next prev parent reply other threads:[~2019-02-20 2:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 10:12 [PATCH v7 0/3] Fixes for Tegra soctherm Wei Ni
2019-01-03 10:12 ` [PATCH v7 1/3] thermal: tegra: remove unnecessary warnings Wei Ni
2019-02-18 9:47 ` Daniel Lezcano
2019-02-19 2:14 ` Wei Ni
2019-01-03 10:12 ` [PATCH v7 2/3] thermal: tegra: fix memory allocation Wei Ni
2019-02-18 10:24 ` Daniel Lezcano
2019-01-03 10:12 ` [PATCH v7 3/3] thermal: tegra: add get_trend ops Wei Ni
2019-02-18 10:27 ` Daniel Lezcano
2019-02-19 2:15 ` Wei Ni
2020-03-30 17:23 ` Daniel Lezcano
2019-01-11 2:20 ` [PATCH v7 0/3] Fixes for Tegra soctherm Wei Ni
2019-01-21 9:17 ` Wei Ni
2019-02-18 7:59 ` Wei Ni
2019-02-20 2:14 ` Zhang Rui [this message]
2019-02-20 8:42 ` 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=1550628841.3372.1.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--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