From: Geert Uytterhoeven <geert@linux-m68k.org>
To: John Madieu <john.madieu.xa@bp.renesas.com>
Cc: niklas.soderlund+renesas@ragnatech.se, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org, rafael@kernel.org,
daniel.lezcano@linaro.org, magnus.damm@gmail.com,
claudiu.beznea.uj@bp.renesas.com, devicetree@vger.kernel.org,
john.madieu@gmail.com, rui.zhang@intel.com,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
biju.das.jz@bp.renesas.com, linux-pm@vger.kernel.org
Subject: Re: [RFC PATCH 1/3] thermal/cpuplog_cooling: Add CPU hotplug cooling driver
Date: Tue, 11 Mar 2025 09:28:01 +0100 [thread overview]
Message-ID: <CAMuHMdWV7CNBJbPKpymBvvQTbHcpSYFA7DfbOr27CRwwGxh18A@mail.gmail.com> (raw)
In-Reply-To: <20250309121324.29633-2-john.madieu.xa@bp.renesas.com>
Hi John,
On Sun, 9 Mar 2025 at 13:14, John Madieu <john.madieu.xa@bp.renesas.com> wrote:
> Add thermal cooling mechanism that dynamically manages CPU online/offline
> states to prevent overheating. It registers per-CPU cooling devices that can
> take CPUs offline when thermal thresholds are excee and that integrates with
> the Linux thermal framework as a cooling devices.
>
> Signed-off-by: John Madieu <john.madieu.xa@bp.renesas.com>
Thanks for your patch!
> --- /dev/null
> +++ b/drivers/thermal/cpuplug_cooling.c
> +static int register_cpu_hotplug_cooling(struct device_node *cpu_node,
> + int cpu_id)
> +{
> + hotplug_cdev = kzalloc(sizeof(*hotplug_cdev), GFP_KERNEL);
> + if (!hotplug_cdev) {
> + pr_err("Failed to allocate memory for cooling device\n");
scripts/checkpatch.pl:
WARNING: Possible unnecessary 'out of memory' message
and checkpatch is right, as the memory core already takes care of
printing a message.
> + return -ENOMEM;
> + }
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2025-03-11 8:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 12:13 [RFC PATCH 0/3] thermal: Add CPU hotplug cooling driver John Madieu
2025-03-09 12:13 ` [RFC PATCH 1/3] thermal/cpuplog_cooling: " John Madieu
2025-03-11 7:30 ` Krzysztof Kozlowski
2025-03-11 11:38 ` John Madieu
2025-03-11 8:28 ` Geert Uytterhoeven [this message]
2025-03-11 11:41 ` John Madieu
2025-03-09 12:13 ` [RFC PATCH 2/3] tmon: Add support for THERMAL_TRIP_PLUG type John Madieu
2025-03-09 12:13 ` [RFC PATCH 3/3] arm64: dts: renesas: r9a09g047: Add thermal hotplug trip point John Madieu
2025-03-11 10:53 ` Christian Loehle
2025-03-11 11:57 ` John Madieu
2025-03-11 15:29 ` Christian Loehle
2025-03-10 10:17 ` [RFC PATCH 0/3] thermal: Add CPU hotplug cooling driver Biju Das
2025-03-11 11:33 ` John Madieu
2025-03-15 14:40 ` 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=CAMuHMdWV7CNBJbPKpymBvvQTbHcpSYFA7DfbOr27CRwwGxh18A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=john.madieu.xa@bp.renesas.com \
--cc=john.madieu@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=rafael@kernel.org \
--cc=robh@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 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).