linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>, linux-pm@vger.kernel.org
Cc: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Rafael J. Wysocki" <rafael@kernel.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 1/2] thermal: rcar_gen3: Add support for per-SoC default trim values
Date: Sun, 31 Aug 2025 19:02:28 +0200	[thread overview]
Message-ID: <f30a88d0-a7f2-45be-a523-bd27597d229f@mailbox.org> (raw)
In-Reply-To: <5ffb67b8-cded-412b-881c-14179c2ba3b8@linaro.org>

On 8/14/25 12:00 AM, Daniel Lezcano wrote:
> On 13/08/2025 22:37, Marek Vasut wrote:
>> On 8/1/25 11:59 AM, Daniel Lezcano wrote:
>>> On 25/06/2025 20:16, Marek Vasut wrote:
>>>> The Working Sample R-Car SoCs may not yet have thermal sensor trimming
>>>> values programmed into fuses, those fuses are blank instead. For such
>>>> SoCs, the driver includes fallback trimming values. Those values are
>>>> currently applied to all SoCs which use this driver.
>>>>
>>>> Introduce support for per-SoC fallback trimming values in preparation
>>>> for SoCs which do not use these current trimming values. No functional
>>>> change is intended here.
>>>>
>>>> Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
>>>> ---
>>>> Cc: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
>>>
>>> Applied, thanks
>> Is this series supposed to be in linux-next by now ?
>>
>> I don't see it either on git.kernel.org thermal group tree or your 
>> tree, where was the series applied to ?
> 
> 
> Sorry I did push the branch.
> 
> It is in the thermal bleeding-edge branch now and will go to linux-next 
> in a couple of days
This still didn't show up in next/master , did something go wrong ?

      parent reply	other threads:[~2025-08-31 17:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 18:16 [PATCH v2 1/2] thermal: rcar_gen3: Add support for per-SoC default trim values Marek Vasut
2025-06-25 18:16 ` [PATCH v2 2/2] thermal: rcar_gen3: Add support for R-Car V4H " Marek Vasut
2025-08-01  9:59 ` [PATCH v2 1/2] thermal: rcar_gen3: Add support for per-SoC " Daniel Lezcano
2025-08-13 20:37   ` Marek Vasut
2025-08-13 22:00     ` Daniel Lezcano
2025-08-14  3:14       ` Marek Vasut
2025-08-31 17:02       ` Marek Vasut [this message]

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=f30a88d0-a7f2-45be-a523-bd27597d229f@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --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=niklas.soderlund+renesas@ragnatech.se \
    --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;
as well as URLs for NNTP newsgroup(s).