From: Eduardo Valentin <eduardo.valentin@ti.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Eduardo Valentin <eduardo.valentin@ti.com>
Subject: [PATCH 00/11] thermal: clean ups on thermal code base
Date: Fri, 22 Mar 2013 17:00:43 -0400 [thread overview]
Message-ID: <1363986054-24637-1-git-send-email-eduardo.valentin@ti.com> (raw)
Hey Rui,
Here is a sequence of fixes and documentation improvements
thermal code base. This should be first of a series of changes
I am planing to send out.
On this very first there is no change in functionality, as
the patches only change symbol names and updates kernel-doc
comments and their formants.
For those interested in testing and trying the driver, these patches are
also available, as usual, here:
git@gitorious.org:thermal-framework/thermal-framework.git thermal_work/thermal_fw/coding_style
https://git.gitorious.org/thermal-framework/thermal-framework.git thermal_work/thermal_fw/coding_style
Eduardo Valentin (11):
thermal: use strlcpy instead of strcpy
thermal: update driver license
thermal: rename notify_thermal_framework to thermal_notify_framework
thermal: rename get_thermal_instance to thermal_instance_get
thermal: rename get_tz_trend to thermal_zone_trend_get
thermal: use EXPORT_SYMBOL_GPL
thermal: update kernel-doc for thermal_zone_bind_cooling_device
thermal: update kernel-doc for thermal_zone_unbind_cooling_device
thermal: update kernel-doc for thermal_cooling_device_register
thermal: update kernel-doc for create_trip_attrs
thermal: update kernel-doc for thermal_zone_device_register
Documentation/thermal/sysfs-api.txt | 6 +-
drivers/thermal/fair_share.c | 2 +-
drivers/thermal/step_wise.c | 2 +-
drivers/thermal/thermal_sys.c | 90 ++++++++++++++++++++++++-----------
include/linux/thermal.h | 6 +-
5 files changed, 70 insertions(+), 36 deletions(-)
--
1.7.7.1.488.ge8e1c
next reply other threads:[~2013-03-22 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 21:00 Eduardo Valentin [this message]
2013-03-22 21:00 ` [PATCH 01/11] thermal: use strlcpy instead of strcpy Eduardo Valentin
2013-03-22 21:00 ` [PATCH 02/11] thermal: update driver license Eduardo Valentin
2013-03-22 21:00 ` [PATCH 03/11] thermal: rename notify_thermal_framework to thermal_notify_framework Eduardo Valentin
2013-03-22 21:00 ` [PATCH 04/11] thermal: rename get_thermal_instance to thermal_instance_get Eduardo Valentin
2013-03-22 21:00 ` [PATCH 05/11] thermal: rename get_tz_trend to thermal_zone_trend_get Eduardo Valentin
2013-03-22 21:00 ` [PATCH 06/11] thermal: use EXPORT_SYMBOL_GPL Eduardo Valentin
2013-03-22 21:00 ` [PATCH 07/11] thermal: update kernel-doc for thermal_zone_bind_cooling_device Eduardo Valentin
2013-03-22 21:00 ` [PATCH 08/11] thermal: update kernel-doc for thermal_zone_unbind_cooling_device Eduardo Valentin
2013-03-22 21:00 ` [PATCH 09/11] thermal: update kernel-doc for thermal_cooling_device_register Eduardo Valentin
2013-03-22 21:00 ` [PATCH 10/11] thermal: update kernel-doc for create_trip_attrs Eduardo Valentin
2013-03-22 21:00 ` [PATCH 11/11] thermal: update kernel-doc for thermal_zone_device_register Eduardo Valentin
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=1363986054-24637-1-git-send-email-eduardo.valentin@ti.com \
--to=eduardo.valentin@ti.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;
as well as URLs for NNTP newsgroup(s).