linux-kernel - Re: [PATCH -next] clk: shmobile: fix sparse NULL pointer warning

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:	Wed, 14 Jan 2015 13:09:10 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	weiyj_lk@....com
Cc:	Mike Turquette <mturquette@...aro.org>,
	Stephen Boyd <sboyd@...eaurora.org>,
	Geert Uytterhoeven <geert+renesas@...der.be>,
	Ulrich Hecht <ulrich.hecht+renesas@...il.com>,
	Wei Yongjun <yongjun_wei@...ndmicro.com.cn>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] clk: shmobile: fix sparse NULL pointer warning

On Wed, Jan 14, 2015 at 09:16:23AM +0800, weiyj_lk@....com wrote:
> From: Wei Yongjun <yongjun_wei@...ndmicro.com.cn>
> 
> Fixes the following sparse warnings:
> 
> drivers/clk/shmobile/clk-sh73a0.c:57:17: warning:
>  Using plain integer as NULL pointer
> 
> Signed-off-by: Wei Yongjun <yongjun_wei@...ndmicro.com.cn>

Acked-by: Simon Horman <horms+renesas@...ge.net.au>

> ---
>  drivers/clk/shmobile/clk-sh73a0.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/clk/shmobile/clk-sh73a0.c b/drivers/clk/shmobile/clk-sh73a0.c
> index 8574a6d..cd529cf 100644
> --- a/drivers/clk/shmobile/clk-sh73a0.c
> +++ b/drivers/clk/shmobile/clk-sh73a0.c
> @@ -54,7 +54,7 @@ static struct div4_clk div4_clks[] = {
>  	{ "m2", "pll1", CPG_FRQCRA,  0 },
>  	{ "zx", "pll1", CPG_FRQCRB, 12 },
>  	{ "hp", "pll1", CPG_FRQCRB,  4 },
> -	{ NULL, 0, 0, 0 },
> +	{ NULL, NULL, 0, 0 },
>  };
>  
>  static const struct clk_div_table div4_div_table[] = {
> 
--
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/