All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
	Lukasz Luba <lukasz.luba@arm.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH v2 0/3] thermal: More separation between the core and drivers
Date: Mon, 25 Mar 2024 14:33:27 +0100	[thread overview]
Message-ID: <42ffcfb8-33fd-4ea5-bfac-fa8c78cd1cd4@linaro.org> (raw)
In-Reply-To: <2331888.ElGaqSPkdT@kreacher>


Hi Rafael,

thank you for this series.

It has been reported a regression with commit cf3986f8c01d3. I'm 
investigating and confirming it. If it is the case a revert may impact 
this series.


On 25/03/2024 14:10, Rafael J. Wysocki wrote:
> Hi Everyone,
> 
> This is an update of
> 
> https://lore.kernel.org/linux-pm/4558384.LvFx2qVVIh@kreacher/
> 
> which is a resend of the series with one extra patch added.  That extra patch
> is related to
> 
> https://lore.kernel.org/linux-pm/20240306085428.88011-1-daniel.lezcano@linaro.org/
> 
> The original description of the first two patches still applies:
> 
>> Patch [1/2] is based on the observation that the threshold field in struct
>> thermal_trip really should be core-internal and to make that happen it
>> introduces a wrapper structure around struct thermal_trip for internal
>> use in the core.
>>
>> Patch [2/2] moves the definition of the new structure and the struct
>> thermal_zone_device one to a local header file in the core to enforce
>> more separation between the core and drivers.
>>
>> The patches are not expected to introduce any observable differences in
>> behavior, so please let me know if you see any of that.
> 

-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  parent reply	other threads:[~2024-03-25 13:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 13:10 [PATCH v2 0/3] thermal: More separation between the core and drivers Rafael J. Wysocki
2024-03-25 13:11 ` [PATCH v2 1/3] thermal: core: Move threshold out of struct thermal_trip Rafael J. Wysocki
2024-03-27 17:37   ` [Update][PATCH v2.1 " Rafael J. Wysocki
2024-03-25 13:12 ` [PATCH v2 2/3] thermal: core: Make struct thermal_zone_device definition internal Rafael J. Wysocki
2024-03-25 13:13 ` [PATCH v2 3/3] thermal: core: Sort trip point crossing notifications by temperature Rafael J. Wysocki
2024-03-25 13:33 ` Daniel Lezcano [this message]
2024-03-25 13:39   ` [PATCH v2 0/3] thermal: More separation between the core and drivers Rafael J. Wysocki
2024-03-25 13:47     ` Daniel Lezcano
2024-03-27 15:44       ` 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=42ffcfb8-33fd-4ea5-bfac-fa8c78cd1cd4@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=stanislaw.gruszka@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.