linux-kernel - Re: [PATCH RESEND 03/11] thermal: rename notify_thermal_framework to thermal_notify

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1366213041.2091.68.camel@rzhang1-mobl4>
Date:	Wed, 17 Apr 2013 23:37:21 +0800
From:	Zhang Rui <rui.zhang@...el.com>
To:	Eduardo Valentin <eduardo.valentin@...com>
Cc:	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND 03/11] thermal: rename notify_thermal_framework
 to thermal_notify_framework

On Mon, 2013-04-08 at 12:07 -0400, Eduardo Valentin wrote:
> To follow the prefix names used by the thermal exported functions,
> this patch renames notify_thermal_framework to thermal_notify_framework.
> 
> Signed-off-by: Eduardo Valentin <eduardo.valentin@...com>

Hmm, I'm okay with this one.

thanks,
rui
> ---
>  Documentation/thermal/sysfs-api.txt |    2 +-
>  drivers/thermal/thermal_sys.c       |    6 +++---
>  include/linux/thermal.h             |    2 +-
>  3 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/thermal/sysfs-api.txt b/Documentation/thermal/sysfs-api.txt
> index 6859661..4b23190 100644
> --- a/Documentation/thermal/sysfs-api.txt
> +++ b/Documentation/thermal/sysfs-api.txt
> @@ -363,7 +363,7 @@ This function returns the thermal_instance corresponding to a given
>  {thermal_zone, cooling_device, trip_point} combination. Returns NULL
>  if such an instance does not exist.
>  
> -5.3:notify_thermal_framework:
> +5.3:thermal_notify_framework:
>  This function handles the trip events from sensor drivers. It starts
>  throttling the cooling devices according to the policy configured.
>  For CRITICAL and HOT trip points, this notifies the respective drivers,
> diff --git a/drivers/thermal/thermal_sys.c b/drivers/thermal/thermal_sys.c
> index 9542600..ffaf6d3 100644
> --- a/drivers/thermal/thermal_sys.c
> +++ b/drivers/thermal/thermal_sys.c
> @@ -1420,7 +1420,7 @@ void thermal_cdev_update(struct thermal_cooling_device *cdev)
>  EXPORT_SYMBOL(thermal_cdev_update);
>  
>  /**
> - * notify_thermal_framework - Sensor drivers use this API to notify framework
> + * thermal_notify_framework - Sensor drivers use this API to notify framework
>   * @tz:		thermal zone device
>   * @trip:	indicates which trip point has been crossed
>   *
> @@ -1431,11 +1431,11 @@ EXPORT_SYMBOL(thermal_cdev_update);
>   * The throttling policy is based on the configured platform data; if no
>   * platform data is provided, this uses the step_wise throttling policy.
>   */
> -void notify_thermal_framework(struct thermal_zone_device *tz, int trip)
> +void thermal_notify_framework(struct thermal_zone_device *tz, int trip)
>  {
>  	handle_thermal_trip(tz, trip);
>  }
> -EXPORT_SYMBOL(notify_thermal_framework);
> +EXPORT_SYMBOL(thermal_notify_framework);
>  
>  /**
>   * create_trip_attrs - create attributes for trip points
> diff --git a/include/linux/thermal.h b/include/linux/thermal.h
> index f0bd7f9..e8ec9d8 100644
> --- a/include/linux/thermal.h
> +++ b/include/linux/thermal.h
> @@ -242,7 +242,7 @@ int get_tz_trend(struct thermal_zone_device *, int);
>  struct thermal_instance *get_thermal_instance(struct thermal_zone_device *,
>  		struct thermal_cooling_device *, int);
>  void thermal_cdev_update(struct thermal_cooling_device *);
> -void notify_thermal_framework(struct thermal_zone_device *, int);
> +void thermal_notify_framework(struct thermal_zone_device *, int);
>  
>  int thermal_register_governor(struct thermal_governor *);
>  void thermal_unregister_governor(struct thermal_governor *);


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/