From: Pavel Machek <pavel@nabladev.com>
To: Ovidiu Panait <ovidiu.panait.rb@renesas.com>
Cc: cip-dev@lists.cip-project.org, pavel@nabladev.com,
nobuhiro.iwamatsu.x90@mail.toshiba
Subject: Re: [PATCH 6.1.y-cip 07/11] thermal/drivers/renesas/rzg3e: Fix add thermal driver for the Renesas RZ/G3E SoC
Date: Mon, 2 Feb 2026 14:29:33 +0100 [thread overview]
Message-ID: <aYCmvU2dsWdrMiG8@duo.ucw.cz> (raw)
In-Reply-To: <20260128132522.6902-8-ovidiu.panait.rb@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]
Hi!
> From: John Madieu <john.madieu.xa@bp.renesas.com>
>
> commit dc67521c20b701b5237ff486ae078829dc1f8fea upstream.
>
> When applied the change commit 19d3a401a617, a conflict appeared
> resulting into a manual fix. However the new file rzg3e_thermal.c was
> not added but stayed locally in source tree and miss to be merged with
> the entire change.
>
> Fix this by adding the file back.
Ok, so you know you made a mistake, but for -cip, it would be
better to put this before the 6/ patch. You can't undo the mistake for
mainline, but ou can do that for -cip :-).
> Fixes: 19d3a401a617 ("Add thermal driver for the Renesas RZ/G3E SoC")
> - used devm_reset_control_get_exclusive() + reset_control_deassert() +
> devm_add_action_or_reset() instead of
> devm_reset_control_get_exclusive_deasserted() as the latter is not
> available in v6.1 CIP; added rzg3e_thermal_reset_assert() action
> function for this
Yep so... this seems to be repeat issue in Renesas patches. Are we
going to hit it again in future? If so, maybe we should introduce
devm_reset_control_get_exclusive_deasserted() to 6.1, too.
> + /* Convert to temperature */
> + *temp = rzg3e_thermal_code_to_temp(priv, code);
> +
> + dev_dbg(priv->dev, "temp=%d mC (%d.%03d°C), code=0x%03x\n",
> + *temp, *temp / 1000, abs(*temp) % 1000, code);
> +
I'd expect dmesg output to be ASCII, not unicode, as it goes over
various serial lines etc. So maybe °C -> degC or just C.
Thanks and best regards,
Pavel
--
In cooperation with Nabla.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-02-02 13:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 13:25 [PATCH 6.1.y-cip 00/11] Add RZ/V2H TSU support Ovidiu Panait
2026-01-28 13:25 ` [PATCH 6.1.y-cip 01/11] soc: renesas: rz-sysc: Add syscon/regmap support Ovidiu Panait
2026-02-02 13:17 ` [cip-dev] " Pavel Machek
2026-01-28 13:25 ` [PATCH 6.1.y-cip 02/11] soc: renesas: r9a09g056-sys: Populate max_register Ovidiu Panait
2026-01-28 13:25 ` [PATCH 6.1.y-cip 03/11] soc: renesas: rz-sysc: Populate readable_reg/writeable_reg in regmap config Ovidiu Panait
2026-02-02 13:19 ` Pavel Machek
2026-01-28 13:25 ` [PATCH 6.1.y-cip 04/11] PM: domains: Add RZ/V2H compatible to PM domain detach list Ovidiu Panait
2026-01-28 13:25 ` [PATCH 6.1.y-cip 05/11] dt-bindings: thermal: r9a09g047-tsu: Document the TSU unit Ovidiu Panait
2026-01-28 13:25 ` [PATCH 6.1.y-cip 06/11] thermal/drivers/renesas/rzg3e: Add thermal driver for the Renesas RZ/G3E SoC Ovidiu Panait
2026-02-02 13:21 ` Pavel Machek
2026-01-28 13:25 ` [PATCH 6.1.y-cip 07/11] thermal/drivers/renesas/rzg3e: Fix add " Ovidiu Panait
2026-02-02 13:29 ` Pavel Machek [this message]
2026-01-28 13:25 ` [PATCH 6.1.y-cip 08/11] arm64: defconfig: Enable the Renesas RZ/G3E thermal driver Ovidiu Panait
2026-01-28 13:25 ` [PATCH 6.1.y-cip 09/11] clk: renesas: r9a09g057: Add clock and reset entries for TSU Ovidiu Panait
2026-01-28 13:25 ` [PATCH 6.1.y-cip 10/11] arm64: dts: renesas: r9a09g057: Move interrupt-parent to root node Ovidiu Panait
2026-01-28 13:25 ` [PATCH 6.1.y-cip 11/11] arm64: dts: renesas: r9a09g057: Add TSU nodes Ovidiu Panait
2026-01-29 8:10 ` [PATCH 6.1.y-cip 00/11] Add RZ/V2H TSU support nobuhiro.iwamatsu.x90
2026-02-02 2:00 ` nobuhiro.iwamatsu.x90
2026-02-02 13:48 ` [cip-dev] " Pavel Machek
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=aYCmvU2dsWdrMiG8@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=ovidiu.panait.rb@renesas.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