linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <eduardo.valentin@ti.com>
To: rui.zhang@intel.com
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Eduardo Valentin <eduardo.valentin@ti.com>
Subject: [PATCHv2 0/9] thermal: clean ups on thermal code base
Date: Tue, 23 Apr 2013 17:48:11 -0400	[thread overview]
Message-ID: <1366753700-1412-1-git-send-email-eduardo.valentin@ti.com> (raw)

Hello Rui,

This is v2 of this series. I have worked on the comments you sent
on these patches. For your reference, v1 has been reviewed at [1].

Summary of changelog:
- Added your acked-by on those patches you granted.
- Fixed the comments regarding functions that are not going
to be exported.
- Removed patches that are touching functions that are not
going to be exported.

Also available, as usual, here:
git@gitorious.org:thermal-framework/thermal-framework.git thermal_work/thermal_core/coding_style
https://git.gitorious.org/thermal-framework/thermal-framework.git thermal_work/thermal_core/coding_style

The above branches are based on linux-next/master.

All best,

[1] - https://lkml.org/lkml/2013/4/8/471

Eduardo Valentin (9):
  thermal: use strlcpy instead of strcpy
  thermal: update driver license
  thermal: rename notify_thermal_framework to thermal_notify_framework
  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 |  2 +-
 drivers/thermal/thermal_core.c      | 80 ++++++++++++++++++++++++++-----------
 include/linux/thermal.h             |  2 +-
 3 files changed, 59 insertions(+), 25 deletions(-)

-- 
1.8.2.1.342.gfa7285d


             reply	other threads:[~2013-04-23 21:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 21:48 Eduardo Valentin [this message]
2013-04-23 21:48 ` [PATCHv2 1/9] thermal: use strlcpy instead of strcpy Eduardo Valentin
2013-04-23 21:48 ` [PATCHv2 2/9] thermal: update driver license Eduardo Valentin
2013-04-23 21:48 ` [PATCHv2 3/9] thermal: rename notify_thermal_framework to thermal_notify_framework Eduardo Valentin
2013-04-23 21:48 ` [PATCHv2 4/9] thermal: use EXPORT_SYMBOL_GPL Eduardo Valentin
2013-04-23 21:48 ` [PATCHv2 5/9] thermal: update kernel-doc for thermal_zone_bind_cooling_device Eduardo Valentin
2013-04-23 21:48 ` [PATCHv2 6/9] thermal: update kernel-doc for thermal_zone_unbind_cooling_device Eduardo Valentin
2013-04-23 21:48 ` [PATCHv2 7/9] thermal: update kernel-doc for thermal_cooling_device_register Eduardo Valentin
2013-04-23 21:48 ` [PATCHv2 8/9] thermal: update kernel-doc for create_trip_attrs Eduardo Valentin
2013-04-23 21:48 ` [PATCHv2 9/9] thermal: update kernel-doc for thermal_zone_device_register Eduardo Valentin
2013-04-24 16:54 ` [PATCHv2 0/9] thermal: clean ups on thermal code base Zhang, Rui

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=1366753700-1412-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).