Message-ID: <516F06F5.9060200@ti.com>
Date: Wed, 17 Apr 2013 16:32:53 -0400
From: Eduardo Valentin <eduardo.valentin@ti.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Zhang, Rui" <rui.zhang@intel.com>
CC: <eduardo.valentin@ti.com>, Amit Daniel Kachhap <amit.daniel@samsung.com>,
        "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
        "linux-kernel@vger.kernel.org >> \"linux-kernel@vger.kernel.org\"" 
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/30] thermal: cpu_cooling: code improvements
References: <1366218743-20841-1-git-send-email-eduardo.valentin@ti.com>
In-Reply-To: <1366218743-20841-1-git-send-email-eduardo.valentin@ti.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 3366
Lines: 74

On 17-04-2013 13:11, Eduardo Valentin wrote:
> Rui,


Looks like I forgot to add the lists on patch 00. Doing so..
>
> This is a series of patches to improve the code for cpu_cooling.
> Majority of these changes are actually kernel-doc updates, as
> they required to be revised. A part from these, there are some
> changes regarding code style and readiness.
>
> Some may complain that these are a matter of taste, indeed.
> But I tried to just be unbiased and just keep the changes related
> to kernel-doc and checkpatch.pl. After this series, theses
> tools should be generating decent output ;-).
>
> The remaining changes are actually a couple of fixes for defensive
> coding. A part from updating the MAINTAINERS entry to cover cpu_cooling.
>
> This series has been tested on TI OMAP4430, together with the
> thermal driver under staging tree.
>
> All these patches are based on current linux-next/master.
>
> They are also available here:
>
> All best,
>
> Eduardo Valentin (30):
>    thermal: cpu_cooling: remove unused headers
>    thermal: cpu_cooling: remove trailing white spaces
>    thermal: cpu_cooling: fix kernel_doc for cpufreq_cooling_device
>    thermal: cpu_cooling: use EXPORT_SYMBOL_GPL
>    thermal: cpu_cooling: remove compiler warning
>    thermal: cpu_cooling: standardize end of function
>    thermal: cpu_cooling: fix kernel doc for is_cpufreq_valid
>    thermal: cpu_cooling: add documentation for get_property
>    thermal: cpu_cooling: standardize comment style
>    thermal: cpu_cooling: align on open parenthesis
>    thermal: cpu_cooling: remove trailing blank line
>    thermal: cpu_cooling: document cpufreq_get_cooling_level
>    thermal: cpu_cooling: remove checkpatch.pl warning
>    thermal: cpu_cooling: improve documentation for get_cpu_frequency
>    thermal: cpu_cooling: update documentation for cpufreq_apply_cooling
>    thermal: cpu_cooling: update documentation for
>      cpufreq_thermal_notifier
>    thermal: cpu_cooling: update Kconfig entry
>    thermal: cpu_cooling: alignment improvements
>    thermal: cpu_cooling: update documentation for cpufreq_get_max_state
>    thermal: cpu_cooling: update documentation for cpufreq_get_cur_state
>    thermal: cpu_cooling: update documentation for cpufreq_set_cur_state
>    thermal: cpu_cooling: update kernel-doc for cpufreq_cooling_register
>    thermal: cpu_cooling: update kernel-doc comment for
>      cpufreq_cooling_unregister
>    thermal: cpu_cooling: use snprintf instead of sprintf
>    thermal: cpu_cooling: remove not needed curl brackets
>    thermal: cpu_cooling: remove unused symbols
>    thermal: cpu_cooling: add needed header for cpu_cooling.h
>    MAINTAINERS: update thermal entry by adding file cpu_cooling.h
>    thermal: cpu_cooling: remove unused symbols on cpu_cooling.h
>    thermal: cpu_cooling: improve line breaking
>
>   MAINTAINERS                   |   1 +
>   drivers/thermal/Kconfig       |   5 +-
>   drivers/thermal/cpu_cooling.c | 156 ++++++++++++++++++++++++++++++------------
>   include/linux/cpu_cooling.h   |  20 +++---
>   4 files changed, 125 insertions(+), 57 deletions(-)
>

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