linux-kernel - [PATCH] C6X: clock: return 0 upon error from clk_round

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

Date:	Tue, 26 Nov 2013 17:04:18 -0800
From:	Paul Walmsley <pwalmsley@...dia.com>
To:	Mark Salter <msalter@...hat.com>,
	Aurelien Jacquiot <a-jacquiot@...com>
CC:	<linux-c6x-dev@...ux-c6x.org>, <linux-kernel@...r.kernel.org>
Subject: [PATCH] C6X: clock: return 0 upon error from clk_round_rate()


clk_round_rate() should return 0 now upon an error, rather than returning 
a negative error code.  This is because clk_round_rate() is being changed 
to return an unsigned return type rather than a signed type, since some 
clock sources can generate rates higher than (2^31)-1 Hz.

Signed-off-by: Paul Walmsley <pwalmsley@...dia.com>
Cc: Mark Salter <msalter@...hat.com>
Cc: Aurelien Jacquiot <a-jacquiot@...com>
---
Applies on v3.13-rc1.  See also:

     http://marc.info/?l=linux-arm-kernel&m=138542591313620&w=2

  arch/c6x/platforms/pll.c |    2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/c6x/platforms/pll.c b/arch/c6x/platforms/pll.c
index 3aa898f7ce4d..79d28dda660a 100644
--- a/arch/c6x/platforms/pll.c
+++ b/arch/c6x/platforms/pll.c
@@ -85,7 +85,7 @@ EXPORT_SYMBOL(clk_get_rate);
  long clk_round_rate(struct clk *clk, unsigned long rate)
  {
  	if (clk == NULL || IS_ERR(clk))
-		return -EINVAL;
+		return 0;

  	if (clk->round_rate)
  		return clk->round_rate(clk, rate);
--
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/