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]
Date:	Sat, 12 Jan 2013 14:27:25 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Viresh Kumar <viresh.kumar@...aro.org>
Cc:	cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
	linux-kernel@...r.kernel.org, linaro-dev@...ts.linaro.org,
	patches@...aro.org
Subject: Re: [PATCH 0/5] Cpufreq Fixes for 3.9

On Saturday, January 12, 2013 10:44:37 AM Viresh Kumar wrote:
> Hi Rafael,
> 
> As requested, i am resending all my cpufreq fixes together. I have added correct
> Tested-by flags.

I have dropped the previous versions and applied this series instead.

There's no need to add a Tested-by for yourself if you sign-off a patch,
though.  Tested-by is information that somebody *in* *addition* to the
original author has tested the patch, because we all should test the patches
we sign-off, right?

Rafael


> Viresh Kumar (5):
>   cpufreq: Manage only online cpus
>   cpufreq: Notify governors when cpus are hot-[un]plugged
>   cpufreq: Don't use cpu removed during cpufreq_driver_unregister
>   cpufreq: Simplify __cpufreq_remove_dev()
>   cpufreq: Simplify cpufreq_add_dev()
> 
>  drivers/cpufreq/cpufreq.c       | 316 +++++++++++++++++-----------------------
>  drivers/cpufreq/cpufreq_stats.c |  27 +++-
>  drivers/cpufreq/freq_table.c    |   9 ++
>  include/linux/cpufreq.h         |  14 +-
>  4 files changed, 178 insertions(+), 188 deletions(-)
> 
> 
-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ