From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] thermal: core: Fix thermal zone initialization and move passive polling management to the core
Date: Tue, 30 Apr 2024 19:32:42 +0100 [thread overview]
Message-ID: <bb351bd3-931f-4acc-831e-2866a535bd9a@arm.com> (raw)
In-Reply-To: <5790995.DvuYhMxLoT@kreacher>
On 4/30/24 16:44, Rafael J. Wysocki wrote:
> Hi Everyone,
>
> This a v2 of the patch at
>
> https://lore.kernel.org/linux-pm/5938055.MhkbZ0Pkbq@kreacher/
>
> with one fix patch added and a couple of changes more in the main patch.
>
> Patch [1/2] fixes the thermal zone initialization in the cases when getting the
> first zone temperature from the sensor is delayed and patch [2/2] is an update
> of the patch above.
>
> Thanks!
>
>
>
I have also tested the IPA and Step-wise - they work.
Tested-by: Lukasz Luba <lukasz.luba@arm.com>
next prev parent reply other threads:[~2024-04-30 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 15:44 [PATCH v2 0/2] thermal: core: Fix thermal zone initialization and move passive polling management to the core Rafael J. Wysocki
2024-04-30 15:45 ` [PATCH v2 1/2] thermal: core: Do not call handle_thermal_trip() if zone temperature is invalid Rafael J. Wysocki
2024-04-30 16:43 ` Lukasz Luba
2024-04-30 15:52 ` [PATCH v2 2/2] thermal: core: Move passive polling management to the core Rafael J. Wysocki
2024-04-30 16:47 ` Lukasz Luba
2024-04-30 18:32 ` Lukasz Luba [this message]
2024-04-30 19:15 ` [PATCH v2 0/2] thermal: core: Fix thermal zone initialization and move " Rafael J. Wysocki
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=bb351bd3-931f-4acc-831e-2866a535bd9a@arm.com \
--to=lukasz.luba@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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).