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:	Mon, 1 Apr 2013 14:53:26 +0800
From:	Shawn Guo <shawn.guo@...aro.org>
To:	Viresh Kumar <viresh.kumar@...aro.org>
CC:	<rjw@...k.pl>, <cpufreq@...r.kernel.org>,
	<linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<linaro-kernel@...ts.linaro.org>, <patches@...aro.org>,
	<robin.randhawa@....com>, <Steve.Bannister@....com>,
	<Liviu.Dudau@....com>, <charles.garcia-tobin@....com>,
	<arvind.chauhan@....com>
Subject: Re: [PATCH] cpufreq: cpufreq-cpu0: Call CPUFREQ_POSTCHANGE notifier
 for failure cases too

On Sat, Mar 30, 2013 at 07:48:07PM +0530, Viresh Kumar wrote:
> Currently we are simply returning from target() if we encounter some error after
> broadcasting CPUFREQ_PRECHANGE notifier. Which looks to be wrong as others might
> depend on POSTCHANGE notifier for their functioning.
> 
> So, better broadcast CPUFREQ_POSTCHANGE notifier for these failure cases too,
> but with old frequency.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>

Acked-by: Shawn Guo <shawn.guo@...aro.org>

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