From: YueHaibing <yuehaibing@huawei.com>
To: <edubezval@gmail.com>, <j-keerthy@ti.com>, <rui.zhang@intel.com>,
<daniel.lezcano@linaro.org>, <amitk@kernel.org>,
<sudipm.mukherjee@gmail.com>
Cc: <linux-pm@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
YueHaibing <yuehaibing@huawei.com>
Subject: [PATCH -next] thermal: ti-soc-thermal: Remove unused function ti_thermal_get_temp()
Date: Wed, 9 Sep 2020 21:44:48 +0800 [thread overview]
Message-ID: <20200909134448.30344-1-yuehaibing@huawei.com> (raw)
commit b263b473bf62 ("thermal: ti-soc-thermal: Remove redundant code")
left behind this, remove it.
Signed-off-by: YueHaibing <yuehaibing@huawei.com>
---
drivers/thermal/ti-soc-thermal/ti-thermal-common.c | 8 --------
1 file changed, 8 deletions(-)
diff --git a/drivers/thermal/ti-soc-thermal/ti-thermal-common.c b/drivers/thermal/ti-soc-thermal/ti-thermal-common.c
index 2ce4b19f312a..93b28c7ce83d 100644
--- a/drivers/thermal/ti-soc-thermal/ti-thermal-common.c
+++ b/drivers/thermal/ti-soc-thermal/ti-thermal-common.c
@@ -106,14 +106,6 @@ static inline int __ti_thermal_get_temp(void *devdata, int *temp)
return ret;
}
-static inline int ti_thermal_get_temp(struct thermal_zone_device *thermal,
- int *temp)
-{
- struct ti_thermal_data *data = thermal->devdata;
-
- return __ti_thermal_get_temp(data, temp);
-}
-
static int __ti_thermal_get_trend(void *p, int trip, enum thermal_trend *trend)
{
struct ti_thermal_data *data = p;
--
2.17.1
next reply other threads:[~2020-09-09 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 13:44 YueHaibing [this message]
2022-03-05 12:50 [PATCH -next] thermal: ti-soc-thermal: Remove unused function ti_thermal_get_temp() YueHaibing
2022-03-05 16:55 ` Bryan Brattlof
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=20200909134448.30344-1-yuehaibing@huawei.com \
--to=yuehaibing@huawei.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sudipm.mukherjee@gmail.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).