linux-kernel - Re: [PATCH] clocksource: sirf: Remove unused variable

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]

Message-ID: <CAGsJ_4zG1ATSbLJ-Zw1YhP9FqVEBaBg0qY=4Or+N1i23bD7MAQ@mail.gmail.com>
Date:	Sun, 11 Jan 2015 22:45:16 +0800
From:	Barry Song <baohua@...nel.org>
To:	Fabio Estevam <festevam@...il.com>
Cc:	Daniel Lezcano <daniel.lezcano@...aro.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] clocksource: sirf: Remove unused variable

2014-12-24 5:33 GMT+08:00 Fabio Estevam <festevam@...il.com>:
> Remove 'timer_div' variable to fix the following build warning:
>
> drivers/clocksource/timer-marco.c: In function 'sirfsoc_marco_timer_init':
> drivers/clocksource/timer-marco.c:260:6: warning: unused variable 'timer_div' [-Wunused-variable]
>
> Signed-off-by: Fabio Estevam <festevam@...il.com>

thanks. but this has been handled by:

http://permalink.gmane.org/gmane.linux.ports.arm.kernel/382514

> ---
>  drivers/clocksource/timer-marco.c | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/drivers/clocksource/timer-marco.c b/drivers/clocksource/timer-marco.c
> index 361a789..3ddb81f 100644
> --- a/drivers/clocksource/timer-marco.c
> +++ b/drivers/clocksource/timer-marco.c
> @@ -257,7 +257,6 @@ static void __init sirfsoc_clockevent_init(void)
>  /* initialize the kernel jiffy timer source */
>  static void __init sirfsoc_marco_timer_init(struct device_node *np)
>  {
> -       u32 timer_div;
>         struct clk *clk;
>
>         clk = of_clk_get(np, 0);
> --
> 1.9.1
>

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