[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gV+NHZiAwQdeG_0Cjg-s1ugdTDJDkhRwZ9AmBsy80Giw@mail.gmail.com>
Date: Mon, 21 Oct 2024 14:03:28 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Markus Elfring <Markus.Elfring@....de>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, linux-pm@...r.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>, "Rafael J. Wysocki" <rjw@...ysocki.net>,
LKML <linux-kernel@...r.kernel.org>, Daniel Lezcano <daniel.lezcano@...aro.org>,
Lukasz Luba <lukasz.luba@....com>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>, Zhang Rui <rui.zhang@...el.com>
Subject: Re: [v2 01/11] thermal: core: Add and use thermal zone guard
On Mon, Oct 21, 2024 at 2:02 PM Markus Elfring <Markus.Elfring@....de> wrote:
>
> >> …
> >>> +++ linux-pm/drivers/thermal/thermal_helpers.c
> >>> @@ -60,13 +60,13 @@ bool thermal_trip_is_bound_to_cdev(struc
> …
> >> …
> >>
> >> Would you become interested to apply a statement
> >> like “guard(mutex)(&cdev->lock);”?
> >
> > Well, please see
> > https://lore.kernel.org/linux-pm/5837621.DvuYhMxLoT@rjwysocki.net/
>
> Will the separation of source code adjustments according to cooling devices
> and thermal zones trigger any related clarifications?
I'm not aware of any.
Powered by blists - more mailing lists