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:	Mon, 16 Dec 2013 14:44:36 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Paul Walmsley <pwalmsley@...dia.com>
Cc:	Santosh Shilimkar <santosh.shilimkar@...com>,
	linux-omap@...r.kernel.org,
	"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] cpufreq: omap: clk_round_rate() can return a zero upon error

On 10 December 2013 07:48, Paul Walmsley <pwalmsley@...dia.com> wrote:
> Treat both negative and zero return values from clk_round_rate() as errors.
> This is needed since subsequent patches will convert clk_round_rate()'s
> return value to be an unsigned type, rather than a signed type, since some
> clock sources can generate rates higher than (2^31)-1 Hz.
>
> Eventually, when calling clk_round_rate(), only a return value of
> zero will be considered a error.  All other values will be
> considered valid rates.  The comparison against values less than
> 0 is kept to preserve the correct behavior in the meantime.
>
> This patch also removes a bogus usage of IS_ERR_VALUE(), which is intended
> to be used only on combination pointer/error code return values; a
> side-benefit.
>
> Signed-off-by: Paul Walmsley <pwalmsley@...dia.com>
> Cc: Santosh Shilimkar <santosh.shilimkar@...com>
> Cc: Viresh Kumar <viresh.kumar@...aro.org>

Acked-by: Viresh Kumar <viresh.kumar@...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