public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: daniel.lezcano@kernel.org, gaurav.kohli@oss.qualcomm.com,
	"Zhang Rui" <rui.zhang@intel.com>,
	"Lukasz Luba" <lukasz.luba@arm.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Lucas Stach" <l.stach@pengutronix.de>,
	"Russell King" <linux+etnaviv@armlinux.org.uk>,
	"Christian Gmeiner" <christian.gmeiner@gmail.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Joel Stanley" <joel@jms.id.au>,
	"Andrew Jeffery" <andrew@codeconstruct.com.au>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	"Benson Leung" <bleung@chromium.org>,
	"Pali Rohár" <pali@kernel.org>,
	"Avi Fishman" <avifishman70@gmail.com>,
	"Tomer Maimon" <tmaimon77@gmail.com>,
	"Tali Perry" <tali.perry1@gmail.com>,
	"Patrick Venture" <venture@google.com>,
	"Nancy Yuen" <yuenn@google.com>,
	"Benjamin Fair" <benjaminfair@google.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Jonathan Hunter" <jonathanh@nvidia.com>,
	"Bjorn Andersson" <andersson@kernel.org>,
	"Konrad Dybcio" <konradybcio@kernel.org>,
	"Amit Daniel Kachhap" <amit.kachhap@gmail.com>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Amit Kucheria" <amitk@kernel.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v3 03/11] thermal/of: Move the node pointer assignation in the OF code file
Date: Tue, 5 May 2026 14:13:10 +0200	[thread overview]
Message-ID: <cf419489-82b1-4b07-9eb4-e8b0ab8ec155@oss.qualcomm.com> (raw)
In-Reply-To: <CAJZ5v0huQ3B4buieAUnbqnbV_fpFBPG3+UgULs0qcK9j44NwSw@mail.gmail.com>

On 5/5/26 12:20, Rafael J. Wysocki wrote:

[ ... ]

>> [1]
>> https://lore.kernel.org/all/20260422174305.2899095-4-daniel.lezcano@oss.qualcomm.com/
> 
> I don't think that adding the init callback is a good idea, sorry.

Ok.

May I create a separate preparatory changes splitting the function and 
then rebase the current series on top of it ? So we end up with smaller 
chunk of changes ?

  reply	other threads:[~2026-05-05 12:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 16:14 [PATCH v3 00/11] Support cooling device with ID in the OF Daniel Lezcano
2026-04-29 16:14 ` [PATCH v3 01/11] thermal/core: Use devm_add_action_or_reset() when registering a cooling device Daniel Lezcano
2026-04-30 19:57   ` Rafael J. Wysocki
2026-04-29 16:14 ` [PATCH v3 02/11] thermal/core: Add a non-OF registering function Daniel Lezcano
2026-04-30 20:04   ` Rafael J. Wysocki
2026-04-29 16:14 ` [PATCH v3 03/11] thermal/of: Move the node pointer assignation in the OF code file Daniel Lezcano
2026-04-30 20:12   ` Rafael J. Wysocki
2026-05-01 12:50     ` Rafael J. Wysocki
2026-05-05 10:07       ` Daniel Lezcano
2026-05-05 10:20         ` Rafael J. Wysocki
2026-05-05 12:13           ` Daniel Lezcano [this message]
2026-05-05 12:15             ` Rafael J. Wysocki
2026-04-29 16:14 ` [PATCH v3 04/11] hwmon:: Use non-OF thermal cooling device register function Daniel Lezcano
2026-04-29 16:14 ` [PATCH v3 05/11] thermal/core: Put of_node field cooling device structure under Kconfig option Daniel Lezcano
2026-04-29 16:14 ` [PATCH v3 06/11] thermal/of: Move OF code where it belongs to Daniel Lezcano
2026-04-29 16:14 ` [PATCH v3 07/11] thermal/of: Rename the devm_thermal_of_cooling_device_register() function Daniel Lezcano
2026-04-29 16:14 ` [PATCH v3 08/11] thermal/of: Introduce cooling device of_index Daniel Lezcano
2026-04-29 16:14 ` [PATCH v3 09/11] thermal/of: Pass the of_index and add a function to register with an index Daniel Lezcano
2026-04-29 16:14 ` [PATCH v3 10/11] thermal/of: Process cooling device index in cooling-spec Daniel Lezcano
2026-04-29 16:14 ` [PATCH v3 11/11] dt-bindings: thermal: cooling-devices: Update support for 3 cells cooling device Daniel Lezcano

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=cf419489-82b1-4b07-9eb4-e8b0ab8ec155@oss.qualcomm.com \
    --to=daniel.lezcano@oss.qualcomm.com \
    --cc=airlied@gmail.com \
    --cc=amit.kachhap@gmail.com \
    --cc=amitk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=avifishman70@gmail.com \
    --cc=benjaminfair@google.com \
    --cc=bleung@chromium.org \
    --cc=christian.gmeiner@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@kernel.org \
    --cc=gaurav.kohli@oss.qualcomm.com \
    --cc=heiko@sntech.de \
    --cc=joel@jms.id.au \
    --cc=jonathanh@nvidia.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux+etnaviv@armlinux.org.uk \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=linux@weissschuh.net \
    --cc=lukasz.luba@arm.com \
    --cc=neil.armstrong@linaro.org \
    --cc=pali@kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=simona@ffwll.ch \
    --cc=tali.perry1@gmail.com \
    --cc=thierry.reding@gmail.com \
    --cc=tmaimon77@gmail.com \
    --cc=venture@google.com \
    --cc=viresh.kumar@linaro.org \
    --cc=yuenn@google.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