From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: rafael@kernel.org
Cc: quic_manafm@quicinc.com, rui.zhang@intel.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Amit Kucheria <amitk@kernel.org>
Subject: Re: [PATCH v2 1/3] thermal/core: Encapsulate the trip point crossed function
Date: Tue, 12 Jul 2022 12:37:45 +0200 [thread overview]
Message-ID: <c1d3ed49-096e-00b5-7100-dc3dca523bb6@linaro.org> (raw)
In-Reply-To: <20220708183210.1334839-1-daniel.lezcano@linaro.org>
On 08/07/2022 20:32, Daniel Lezcano wrote:
> The routine where the trip point crossed is detected is a strategic
> place where different processing will happen. Encapsulate the code in
> a function, so all specific actions related with a trip point crossed
> can be grouped.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> ---
Is it ok if I pick this series?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2022-07-12 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 18:32 [PATCH v2 1/3] thermal/core: Encapsulate the trip point crossed function Daniel Lezcano
2022-07-08 18:32 ` [PATCH v2 2/3] thermal/core: Passing a parameter instead of calling the function again Daniel Lezcano
2022-07-12 11:14 ` Lukasz Luba
2022-07-12 18:16 ` Rafael J. Wysocki
2022-07-08 18:32 ` [PATCH v2 3/3] thermal/core: Fix thermal trip cross point Daniel Lezcano
2022-07-12 11:29 ` Lukasz Luba
2022-07-12 12:30 ` Daniel Lezcano
2022-07-12 12:40 ` Lukasz Luba
2022-07-12 13:06 ` Daniel Lezcano
2022-07-12 14:28 ` Lukasz Luba
2022-07-12 10:37 ` Daniel Lezcano [this message]
2022-07-12 11:13 ` [PATCH v2 1/3] thermal/core: Encapsulate the trip point crossed function Lukasz Luba
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=c1d3ed49-096e-00b5-7100-dc3dca523bb6@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amitk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_manafm@quicinc.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.