linux-kernel - Re: [Update][PATCH] cpufreq: Do not hold driver module references for additional policy CPUs

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] [day] [month] [year] [list]

Date:	Fri, 02 Aug 2013 20:16:01 +0530
From:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
To:	Viresh Kumar <viresh.kumar@...aro.org>
CC:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux PM list <linux-pm@...r.kernel.org>,
	cpufreq@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>
Subject: Re: [Update][PATCH] cpufreq: Do not hold driver module references
 for additional policy CPUs

On 08/02/2013 08:08 PM, Viresh Kumar wrote:
> On 2 August 2013 19:01, Rafael J. Wysocki <rjw@...k.pl> wrote:
>> Care to add a changelog?
>>
>> I'll apply this on top of my $subject patch, then.
> 
> I thought you will merge this one with your patch, but there is no
> harm in getting one more on my name :)
> 
> Changelog is (patch attached):
> 
> From: Viresh Kumar <viresh.kumar@...aro.org>
> Date: Fri, 2 Aug 2013 16:17:33 +0530
> Subject: [PATCH] cpufreq: Pass policy to cpufreq_add_policy_cpu()
> 
> Caller of cpufreq_add_policy_cpu() already has pointer to policy structure and
> so there is no need to find it again in cpufreq_add_policy_cpu(). Lets pass it
> directly.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
> ---

The patch looks good.

Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat@...ux.vnet.ibm.com>

Regards,
Srivatsa S. Bhat

>  drivers/cpufreq/cpufreq.c | 18 ++++++------------
>  1 file changed, 6 insertions(+), 12 deletions(-)
> 

--
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/