From: Bryan Brattlof <bb@ti.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: <edubezval@gmail.com>, <j-keerthy@ti.com>, <rafael@kernel.org>,
<daniel.lezcano@linaro.org>, <amitk@kernel.org>,
<rui.zhang@intel.com>, <romain.naour@smile.fr>,
<linux-pm@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] thermal: ti-soc-thermal: Remove unused function ti_thermal_get_temp()
Date: Sat, 5 Mar 2022 10:55:30 -0600 [thread overview]
Message-ID: <20220305165530.lro7ups4xv2injik@bryanbrattlof.com> (raw)
In-Reply-To: <20220305125047.26948-1-yuehaibing@huawei.com>
On March 5, 2022, thus sayeth YueHaibing:
> commit b263b473bf62 ("thermal: ti-soc-thermal: Remove redundant code")
> left behind this, remove it.
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Reviewed-by: Bryan Brattlof <bb@ti.com>
thanks for helping clean the codebase :)
~Bryan
> ---
> 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 0959632b2170..703039d8b937 100644
> --- a/drivers/thermal/ti-soc-thermal/ti-thermal-common.c
> +++ b/drivers/thermal/ti-soc-thermal/ti-thermal-common.c
> @@ -107,14 +107,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 prev parent reply other threads:[~2022-03-05 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-09 13:44 YueHaibing
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=20220305165530.lro7ups4xv2injik@bryanbrattlof.com \
--to=bb@ti.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=rafael@kernel.org \
--cc=romain.naour@smile.fr \
--cc=rui.zhang@intel.com \
--cc=yuehaibing@huawei.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).