Linux Power Management development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: "Marek Vasut" <marek.vasut+renesas@mailbox.org>,
	linux-pm@vger.kernel.org,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Daniel Lezcano" <daniel.lezcano@linaro.org>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Lukasz Luba" <lukasz.luba@arm.com>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	"Zhang Rui" <rui.zhang@intel.com>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2] thermal/drivers/rcar_gen3: Document R-Car Gen4 and RZ/G2 support in driver comment
Date: Thu, 16 Oct 2025 10:01:42 +0200	[thread overview]
Message-ID: <aPCmZp8sM5oV2jPa@shikoro> (raw)
In-Reply-To: <62670d89-56f2-419e-8f80-0536858415f3@mailbox.org>


> > I am not opposed to the patch. Just want to mention that such
> > information gets stale all the time, so I would suggest:
> > 
> > + R-Car Gen3 THS and compatible thermal sensor driver
> This won't cover RZ/G2 which something else, and Gen5 seems like it will be
> also a bit different, so maybe the list is now exhaustive?

Sorry, I don't understand: If RZ/xx THS is compatible with R-Car Gen3
THS, why is this not covered?


  parent reply	other threads:[~2025-10-16  8:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 15:58 [PATCH v2] thermal/drivers/rcar_gen3: Document R-Car Gen4 and RZ/G2 support in driver comment Marek Vasut
2025-10-15 17:33 ` Niklas Söderlund
2025-10-15 18:11   ` Marek Vasut
2025-11-10 11:54     ` Daniel Lezcano
2025-11-10 14:31       ` Marek Vasut
2025-10-15 17:47 ` Wolfram Sang
2025-10-15 18:12   ` Marek Vasut
2025-10-16  7:52     ` Geert Uytterhoeven
2025-10-16  8:01     ` Wolfram Sang [this message]
2025-10-16  8:14       ` Biju Das
2025-10-16  8:20         ` wsa+renesas
2025-10-16  9:58           ` Marek Vasut

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=aPCmZp8sM5oV2jPa@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=magnus.damm@gmail.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=marek.vasut@mailbox.org \
    --cc=niklas.soderlund@ragnatech.se \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox