From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: rafael@kernel.org
Cc: linux-pm@vger.kernel.org, thierry.reding@gmail.com,
linux-kernel@vger.kernel.org,
srinivas.pandruvada@linux.intel.com
Subject: Re: [PATCH v2 0/4] One more step to the thermal zone structure encapsulation
Date: Thu, 13 Jul 2023 11:33:11 +0200 [thread overview]
Message-ID: <82b2d4dc-4583-925a-9e3c-77ae30d0d261@linaro.org> (raw)
In-Reply-To: <20230707203731.848188-1-daniel.lezcano@linaro.org>
On 07/07/2023 22:37, Daniel Lezcano wrote:
> The series provides more changes to self-encapsulate the thermal zone device
> structure in order to protect wild accesses to the thermal zone device
> internals, especially the trip points and the locks.
>
> The first patch adds a macro to warn at compilation time if the
> thermal_core.h is included in a file not belonging to the thermal core
> code. One warning will happen with the nvidia drivers but this is in
> the way to be solved.
>
> The second patch reorders the headers inclusion in the core code.
>
> The next patches makes the int340x drivers to use the thermal trip
> update above and the different accessors for thermal zone structure.
>
> Daniel Lezcano (4):
> thermal/core: Hardening the self-encapsulation
> thermal/core: Reorder the headers inclusion
> thermal/drivers/int3400: Use thermal zone device wrappers
> thermal/drivers/int340x: Do not check the thermal zone state
>
> drivers/thermal/gov_bang_bang.c | 1 +
> drivers/thermal/gov_fair_share.c | 1 +
> drivers/thermal/gov_power_allocator.c | 7 +--
> drivers/thermal/gov_step_wise.c | 1 +
> drivers/thermal/gov_user_space.c | 1 +
> .../intel/int340x_thermal/int3400_thermal.c | 44 +++++++++----------
> drivers/thermal/thermal_acpi.c | 1 +
> drivers/thermal/thermal_core.c | 7 +--
> drivers/thermal/thermal_core.h | 4 ++
> drivers/thermal/thermal_helpers.c | 1 +
> drivers/thermal/thermal_hwmon.c | 1 +
> drivers/thermal/thermal_netlink.c | 1 +
> drivers/thermal/thermal_of.c | 1 +
> drivers/thermal/thermal_sysfs.c | 1 +
> drivers/thermal/thermal_trip.c | 1 +
> 15 files changed, 45 insertions(+), 28 deletions(-)
Applied
--
<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:[~2023-07-13 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 20:37 Daniel Lezcano
2023-07-07 20:37 ` [PATCH v2 1/4] thermal/core: Hardening the self-encapsulation Daniel Lezcano
2023-07-07 20:37 ` [PATCH v2 2/4] thermal/core: Reorder the headers inclusion Daniel Lezcano
2023-07-07 20:37 ` [PATCH v2 3/4] thermal/drivers/int3400: Use thermal zone device wrappers Daniel Lezcano
2023-07-07 20:37 ` [PATCH v2 4/4] thermal/drivers/int340x: Do not check the thermal zone state Daniel Lezcano
2023-07-13 9:33 ` Daniel Lezcano [this message]
2023-07-13 11:30 ` [PATCH v2 0/4] One more step to the thermal zone structure encapsulation Rafael J. Wysocki
2023-07-13 12:24 ` Daniel Lezcano
2023-07-13 13:02 ` Rafael J. Wysocki
2023-07-13 14:15 ` Daniel Lezcano
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=82b2d4dc-4583-925a-9e3c-77ae30d0d261@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.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®