linux-kernel - Re: [PATCH baohua] ASoC: sirf: atlas7: atlas7_iacc_dai

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: <20150205171159.GY21293@sirena.org.uk>
Date:	Thu, 5 Feb 2015 17:11:59 +0000
From:	Mark Brown <broonie@...nel.org>
To:	kbuild test robot <fengguang.wu@...el.com>
Cc:	Rongjun Ying <rongjun.ying@....com>, kbuild-all@...org,
	Barry Song <Barry.Song@....com>,
	Liam Girdwood <lgirdwood@...il.com>,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
	alsa-devel@...a-project.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH baohua] ASoC: sirf: atlas7: atlas7_iacc_dai_ops can be
 static

On Fri, Feb 06, 2015 at 01:03:52AM +0800, kbuild test robot wrote:
> sound/soc/sirf/atlas7-iacc.c:168:24: sparse: symbol 'atlas7_iacc_dai_ops' was not declared. Should it be static?

This file isn't in an upstream tree, should this patch have been sent
upstream (I suspect non-upstream trees may need a bit of filtering in
the scripts)?

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)