From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: daniel.lezcano@linaro.org, rui.zhang@intel.com
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
lukasz.luba@arm.com, srinivas.pandruvada@linux.intel.com,
kai.heng.feng@canonical.com
Subject: [PATCH RFC 4/4] thermal/core: Remove notify ops
Date: Wed, 9 Dec 2020 16:34:40 +0100 [thread overview]
Message-ID: <20201209153440.27643-4-daniel.lezcano@linaro.org> (raw)
In-Reply-To: <20201209153440.27643-1-daniel.lezcano@linaro.org>
With the remove of the notify user in a previous patch, the ops is no
longer needed, remove it.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
---
drivers/thermal/thermal_core.c | 3 ---
include/linux/thermal.h | 2 --
2 files changed, 5 deletions(-)
diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
index 0366f3f076cc..8a47369f0432 100644
--- a/drivers/thermal/thermal_core.c
+++ b/drivers/thermal/thermal_core.c
@@ -406,9 +406,6 @@ static void handle_critical_trips(struct thermal_zone_device *tz,
trace_thermal_zone_trip(tz, trip, trip_type);
- if (tz->ops->notify)
- tz->ops->notify(tz, trip, trip_type);
-
if (trip_type == THERMAL_TRIP_HOT && tz->ops->hot)
tz->ops->hot(tz);
else if (trip_type == THERMAL_TRIP_CRITICAL)
diff --git a/include/linux/thermal.h b/include/linux/thermal.h
index 125c8a4d52e6..7e051b4cf715 100644
--- a/include/linux/thermal.h
+++ b/include/linux/thermal.h
@@ -77,8 +77,6 @@ struct thermal_zone_device_ops {
int (*set_emul_temp) (struct thermal_zone_device *, int);
int (*get_trend) (struct thermal_zone_device *, int,
enum thermal_trend *);
- int (*notify) (struct thermal_zone_device *, int,
- enum thermal_trip_type);
void (*hot)(struct thermal_zone_device *);
void (*critical)(struct thermal_zone_device *);
};
--
2.17.1
next prev parent reply other threads:[~2020-12-09 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 15:34 [PATCH RFC 1/4] thermal/core: Emit a warning if the thermal zone is updated without ops Daniel Lezcano
2020-12-09 15:34 ` [PATCH RFC 2/4] thermal/core: Add critical and hot ops Daniel Lezcano
2020-12-10 9:28 ` Kai-Heng Feng
2020-12-09 15:34 ` [PATCH RFC 3/4] thermal/drivers/acpi: Use hot and critical ops Daniel Lezcano
2020-12-09 15:34 ` Daniel Lezcano [this message]
2020-12-09 15:53 ` [PATCH RFC 1/4] thermal/core: Emit a warning if the thermal zone is updated without ops Lukasz Luba
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=20201209153440.27643-4-daniel.lezcano@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@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;
as well as URLs for NNTP newsgroup(s).