From: Wei Ni <wni@nvidia.com>
To: <rui.zhang@intel.com>, <edubezval@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2] thermal: consistently use int for trip temp
Date: Tue, 8 Mar 2016 11:24:39 +0800 [thread overview]
Message-ID: <56DE45F7.6060307@nvidia.com> (raw)
In-Reply-To: <56DD3A84.4080304@nvidia.com>
On 2016年03月07日 16:23, Wei Ni wrote:
> There had a build error in previous patch.
> Fixed it in this version.
> Please review it.
Add CC: linux-pm@vger.kernel.org
>
> Thanks.
> Wei.
>
> On 2016年03月03日 17:33, Wei Ni wrote:
>> The commit 17e8351a7739 consistently use int for temperature,
>> however it missed a few in trip temperature and thermal_core.
>>
>> In current codes, the trip->temperature used "unsigned long"
>> and zone->temperature used"int", if the temperature is negative
>> value, it will get wrong result when compare temperature with
>> trip temperature.
>>
>> This patch can fix it.
>>
>> Signed-off-by: Wei Ni <wni@nvidia.com>
>> ---
>> drivers/thermal/thermal_core.c | 8 ++++----
>> include/linux/thermal.h | 4 ++--
>> 2 files changed, 6 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
>> index a0a8fd1235e2..e838786fedd8 100644
>> --- a/drivers/thermal/thermal_core.c
>> +++ b/drivers/thermal/thermal_core.c
>> @@ -684,7 +684,7 @@ trip_point_temp_store(struct device *dev, struct device_attribute *attr,
>> {
>> struct thermal_zone_device *tz = to_thermal_zone(dev);
>> int trip, ret;
>> - unsigned long temperature;
>> + int temperature;
>>
>> if (!tz->ops->set_trip_temp)
>> return -EPERM;
>> @@ -692,7 +692,7 @@ trip_point_temp_store(struct device *dev, struct device_attribute *attr,
>> if (!sscanf(attr->attr.name, "trip_point_%d_temp", &trip))
>> return -EINVAL;
>>
>> - if (kstrtoul(buf, 10, &temperature))
>> + if (kstrtoint(buf, 10, &temperature))
>> return -EINVAL;
>>
>> ret = tz->ops->set_trip_temp(tz, trip, temperature);
>> @@ -895,9 +895,9 @@ emul_temp_store(struct device *dev, struct device_attribute *attr,
>> {
>> struct thermal_zone_device *tz = to_thermal_zone(dev);
>> int ret = 0;
>> - unsigned long temperature;
>> + int temperature;
>>
>> - if (kstrtoul(buf, 10, &temperature))
>> + if (kstrtoint(buf, 10, &temperature))
>> return -EINVAL;
>>
>> if (!tz->ops->set_emul_temp) {
>> diff --git a/include/linux/thermal.h b/include/linux/thermal.h
>> index e13a1ace50e9..eee0b7ddd2c1 100644
>> --- a/include/linux/thermal.h
>> +++ b/include/linux/thermal.h
>> @@ -350,8 +350,8 @@ struct thermal_zone_of_device_ops {
>>
>> struct thermal_trip {
>> struct device_node *np;
>> - unsigned long int temperature;
>> - unsigned long int hysteresis;
>> + int temperature;
>> + int hysteresis;
>> enum thermal_trip_type type;
>> };
>>
>>
next prev parent reply other threads:[~2016-03-08 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 9:33 [PATCH v2] thermal: consistently use int for trip temp Wei Ni
2016-03-07 8:23 ` Wei Ni
2016-03-08 3:24 ` Wei Ni [this message]
2016-03-08 21:09 ` Eduardo Valentin
2016-03-14 9:44 ` Wei Ni
2016-04-12 8:51 ` Wei Ni
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=56DE45F7.6060307@nvidia.com \
--to=wni@nvidia.com \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@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