mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	 Lukasz Luba <lukasz.luba@arm.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Subject: Re: [PATCH v1] thermal: intel: int340x_thermal: Use thermal zone accessor functions
Date: Tue, 05 Mar 2024 06:58:26 -0800	[thread overview]
Message-ID: <ea2f6883e29453e9bdb134a183a0747ec06971f1.camel@linux.intel.com> (raw)
In-Reply-To: <2724753.mvXUDI8C0e@kreacher>

On Tue, 2024-03-05 at 12:32 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> Make int340x_thermal use the dedicated accessor functions for the
> thermal zone device object address and the thermal zone type string.
> 
> This is requisite for future thermal core improvements.
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
 Reviewed-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>

> ---
>  drivers/thermal/intel/int340x_thermal/int340x_thermal_zone.c |    3
> ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> Index: linux-
> pm/drivers/thermal/intel/int340x_thermal/int340x_thermal_zone.c
> ===================================================================
> --- linux-
> pm.orig/drivers/thermal/intel/int340x_thermal/int340x_thermal_zone.c
> +++ linux-
> pm/drivers/thermal/intel/int340x_thermal/int340x_thermal_zone.c
> @@ -58,7 +58,8 @@ static int int340x_thermal_set_trip_temp
>  
>  static void int340x_thermal_critical(struct thermal_zone_device
> *zone)
>  {
> -       dev_dbg(&zone->device, "%s: critical temperature reached\n",
> zone->type);
> +       dev_dbg(thermal_zone_device(zone), "%s: critical temperature
> reached\n",
> +               thermal_zone_device_type(zone));
>  }
>  
>  static inline void *int_to_trip_priv(int i)
> 
> 
> 


      reply	other threads:[~2024-03-05 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 11:32 Rafael J. Wysocki
2024-03-05 14:58 ` srinivas pandruvada [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=ea2f6883e29453e9bdb134a183a0747ec06971f1.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome