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]
Message-ID: <20140108110603.GG19974@lee--X1>
Date:	Wed, 8 Jan 2014 11:06:03 +0000
From:	Lee Jones <lee.jones@...aro.org>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Wei Yongjun <weiyj.lk@...il.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	Mark Brown <broonie@...nel.org>,
	"perex@...ex.cz" <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
	Fabio Baltieri <fabio.baltieri@...aro.org>,
	Arnd Bergmann <arnd@...db.de>,
	Wei Yongjun <yongjun_wei@...ndmicro.com.cn>,
	"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -next] ASoC: ux500: Fix sparse non static symbol warning

On Wed, 08 Jan 2014, Linus Walleij wrote:

> On Wed, Jan 8, 2014 at 11:13 AM, Wei Yongjun <weiyj.lk@...il.com> wrote:
> > From: Wei Yongjun <yongjun_wei@...ndmicro.com.cn>
> >
> > Fixes the following sparse warning:
> >
> > sound/soc/ux500/ux500_msp_i2s.c:649:5: warning:
> >  symbol 'ux500_msp_i2s_of_init_msp' was not declared. Should it be static?
> >
> > Signed-off-by: Wei Yongjun <yongjun_wei@...ndmicro.com.cn>

FWIW: Acked-by: Lee Jones <lee.jones@...aro.org>

> Lee, is this something that needs to go along with your patches to
> ASoC or can I apply this separately?

If Mark takes it, then it will just apply as my patches have already
been applied.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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