From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Daniel Lezcano <daniel.lezcano@linexp.org>
Cc: daniel.lezcano@linaro.org, rafael@kernel.org,
khilman@baylibre.com, abailon@baylibre.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Amit Kucheria" <amitk@kernel.org>,
"Zhang Rui" <rui.zhang@intel.com>,
"Jonathan Corbet" <corbet@lwn.net>, "Len Brown" <lenb@kernel.org>,
"Raju Rangoju" <rajur@chelsio.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Ido Schimmel" <idosch@nvidia.com>,
"Petr Machata" <petrm@nvidia.com>,
"Luca Coelho" <luciano.coelho@intel.com>,
"Kalle Valo" <kvalo@kernel.org>, "Peter Kaestle" <peter@piie.net>,
"Hans de Goede" <hdegoede@redhat.com>,
"Mark Gross" <markgross@kernel.org>,
"Sebastian Reichel" <sre@kernel.org>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Support Opensource" <support.opensource@diasemi.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Miri Korenblit" <miriam.rachel.korenblit@intel.com>,
"Johannes Berg" <johannes.berg@intel.com>,
"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
"Sumeet Pawnikar" <sumeet.r.pawnikar@intel.com>,
"Dan Carpenter" <dan.carpenter@oracle.com>,
"Chuansheng Liu" <chuansheng.liu@intel.com>,
"Jiasheng Jiang" <jiasheng@iscas.ac.cn>,
"Antoine Tenart" <atenart@kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list:ACPI THERMAL DRIVER" <linux-acpi@vger.kernel.org>,
"open list:CXGB4 ETHERNET DRIVER (CXGB4)"
<netdev@vger.kernel.org>,
"open list:INTEL WIRELESS WIFI LINK (iwlwifi)"
<linux-wireless@vger.kernel.org>,
"open list:ACER ASPIRE ONE TEMPERATURE AND FAN DRIVER"
<platform-driver-x86@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:RENESAS R-CAR THERMAL DRIVERS"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v2 01/14] thermal/core: Change thermal_zone_ops to thermal_sensor_ops
Date: Sun, 8 May 2022 13:26:21 +0300 [thread overview]
Message-ID: <YneazaFEg3nONazs@smile.fi.intel.com> (raw)
In-Reply-To: <20220507125443.2766939-2-daniel.lezcano@linexp.org>
On Sat, May 07, 2022 at 02:54:29PM +0200, Daniel Lezcano wrote:
> A thermal zone is software abstraction of a sensor associated with
> properties and cooling devices if any.
>
> The fact that we have thermal_zone and thermal_zone_ops mixed is
> confusing and does not clearly identify the different components
> entering in the thermal management process. A thermal zone appears to
> be a sensor while it is not.
>
> In order to set the scene for multiple thermal sensors aggregated into
> a single thermal zone. Rename the thermal_zone_ops to
> thermal_sensor_ops, that will appear clearyl the thermal zone is not a
> sensor but an abstraction of one [or multiple] sensor(s).
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
for whatever drivers in this series I have somehow been involved into.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-05-08 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220507125443.2766939-1-daniel.lezcano@linexp.org>
2022-05-07 12:54 ` [PATCH v2 01/14] thermal/core: Change thermal_zone_ops to thermal_sensor_ops Daniel Lezcano
2022-05-08 10:26 ` Andy Shevchenko [this message]
2022-05-09 9:20 ` Geert Uytterhoeven
2022-05-17 15:42 ` Rafael J. Wysocki
2022-05-17 16:50 ` srinivas pandruvada
2022-05-17 18:53 ` Rafael J. Wysocki
2022-05-17 19:02 ` srinivas pandruvada
2022-05-17 19:07 ` Rafael J. Wysocki
2022-06-26 17:33 ` 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=YneazaFEg3nONazs@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=abailon@baylibre.com \
--cc=amitk@kernel.org \
--cc=atenart@kernel.org \
--cc=chuansheng.liu@intel.com \
--cc=corbet@lwn.net \
--cc=dan.carpenter@oracle.com \
--cc=daniel.lezcano@linaro.org \
--cc=daniel.lezcano@linexp.org \
--cc=davem@davemloft.net \
--cc=festevam@gmail.com \
--cc=hdegoede@redhat.com \
--cc=idosch@nvidia.com \
--cc=jiasheng@iscas.ac.cn \
--cc=johannes.berg@intel.com \
--cc=kernel@pengutronix.de \
--cc=khilman@baylibre.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=markgross@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=miriam.rachel.korenblit@intel.com \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=pabeni@redhat.com \
--cc=peter@piie.net \
--cc=petrm@nvidia.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rajur@chelsio.com \
--cc=rui.zhang@intel.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=sre@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=sumeet.r.pawnikar@intel.com \
--cc=support.opensource@diasemi.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).