linux-kernel - Re: [PATCH] clk: mxs: Fix sparse warnings

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:	Tue, 19 Mar 2013 13:10:28 -0700
From:	Mike Turquette <mturquette@...aro.org>
To:	Shawn Guo <shawn.guo@...aro.org>,
	Fabio Estevam <festevam@...il.com>
Cc:	<linux-kernel@...r.kernel.org>,
	Fabio Estevam <fabio.estevam@...escale.com>
Subject: Re: [PATCH] clk: mxs: Fix sparse warnings

Quoting Shawn Guo (2013-02-17 00:02:20)
> On Mon, Feb 11, 2013 at 12:07:16PM -0200, Fabio Estevam wrote:
> > From: Fabio Estevam <fabio.estevam@...escale.com>
> > 
> > Fix the following sparse warnings:
> > 
> > drivers/clk/mxs/clk.c:17:1: warning: symbol 'mxs_lock' was not declared. Should it be static?
> > drivers/clk/mxs/clk.c:19:5: warning: symbol 'mxs_clk_wait' was not declared. Should it be static?
> > 
> > Signed-off-by: Fabio Estevam <fabio.estevam@...escale.com>
> 
> Acked-by: Shawn Guo <shawn.guo@...aro.org>
> 

Taken into clk-next.

Thanks,
Mike

> > ---
> >  drivers/clk/mxs/clk.c |    1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/clk/mxs/clk.c b/drivers/clk/mxs/clk.c
> > index b24d560..5301bce 100644
> > --- a/drivers/clk/mxs/clk.c
> > +++ b/drivers/clk/mxs/clk.c
> > @@ -13,6 +13,7 @@
> >  #include <linux/io.h>
> >  #include <linux/jiffies.h>
> >  #include <linux/spinlock.h>
> > +#include "clk.h"
> >  
> >  DEFINE_SPINLOCK(mxs_lock);
> >  
> > -- 
> > 1.7.9.5
> >
--
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/