ASoC: samsung: change neo1973_audio from a global to static
Subsystems (3)
PATCH 1/1 ASoC: samsung: change neo1973_audio from a global to static
sparse reportssound/soc/samsung/neo1973_wm8753.c:347:24: warning: symbol 'neo1973_audio' was not declared. Should it be static?
neo1973_audio is only used in neo1973_wm8753.c, so it's storage class specifier should be static.
--- sound/soc/samsung/neo1973_wm8753.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/samsung/neo1973_wm8753.c +1 -1
@@ -344,7 +344,7 @@ static int neo1973_probe(struct platform_device *pdev)return devm_snd_soc_register_card (dev, &neo1973); } -struct platform_driver neo1973_audio = { +static struct platform_driver neo1973_audio = { .driver = { .name ="neo1973-audio" , .pm = &snd_soc_pm_ops,
Signature · 1 line
2.27.0
Quoted 9 lines · Tom Rix
sparse reports
sound/soc/samsung/neo1973_wm8753.c:347:24: warning: symbol 'neo1973_audio' was not declared. Should it be static?
neo1973_audiois only used inneo1973_wm8753.c, so it's storage class specifier should be static.Fixes e26a2abcc246 ("ASoC: samsung: neo1973: turn into platform driver")Signed-off-by Tom Rix <[email protected]>---
Compile testing works!
Best regards,
Krzysztof
Mark Brown
maintainerQuoted 8 lines · Tom Rix
sparse reports
sound/soc/samsung/neo1973_wm8753.c:347:24: warning: symbol 'neo1973_audio' was not declared. Should it be static?
neo1973_audiois only used inneo1973_wm8753.c, so it's storage class specifier should be static.[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: samsung: change neo1973_audio from a global to static
commit: 871325d800ed532ba5874257f04bb4ae75125bc4
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark