From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Lukasz Luba <lukasz.luba@arm.com>, Armin Wolf <w_armin@gmx.de>
Subject: [PATCH v3 0/6] thermal: core: Fixes, simplifications and suspend/resume relocation
Date: Mon, 06 Apr 2026 18:04:56 +0200 [thread overview]
Message-ID: <5119690.31r3eYUQgx@rafael.j.wysocki> (raw)
Hi All,
This is an update of
https://lore.kernel.org/linux-pm/6277980.lOV4Wx5bFT@rafael.j.wysocki/
that adds two fixes to it and updates the last two patches of the
original series.
This series is intended for 7.1 (it applies on top of linux-next).
If fixes the thermal zone removal and registration rollback path by
addressing race possible race conditions and a memory leak in that
core (patches [1-2/6]), removes a redundant check (patch [3/6]), changes
the thermal workqueue to an unbound and non-freezable one (patch [4/6]),
changes the allocation of thermal_class to static (patch [5/4]), and
relocates the suspend and resume of thermal zones closer to the suspend
and resume of devices, respectively (patch [6/6]).
Thanks!
next reply other threads:[~2026-04-06 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 16:04 Rafael J. Wysocki [this message]
2026-04-06 16:07 ` [PATCH v3 1/6] thermal: core: Fix thermal zone governor cleanup issues Rafael J. Wysocki
2026-04-06 16:09 ` [PATCH v3 2/6] thermal: core: Free thermal zone ID later during removal Rafael J. Wysocki
2026-04-06 16:10 ` [PATCH v3 3/6] thermal: core: Drop redundant check from thermal_zone_device_update() Rafael J. Wysocki
2026-04-06 16:11 ` [PATCH v3 4/6] thermal: core: Change thermal_wq to be unbound and not freezable Rafael J. Wysocki
2026-04-06 16:14 ` [PATCH v3 5/6] thermal: core: Allocate thermal_class statically Rafael J. Wysocki
2026-04-06 16:16 ` [PATCH v3 6/6] thermal: core: Suspend thermal zones later and resume them earlier Rafael J. Wysocki
2026-04-06 21:40 ` Armin Wolf
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=5119690.31r3eYUQgx@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=w_armin@gmx.de \
/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