[PATCH] ASoC: dapm: unexport snd_soc_dapm_init()

Masahiro Yamada posted 1 patch 1 year ago
sound/soc/soc-dapm.c | 1 -
1 file changed, 1 deletion(-)
[PATCH] ASoC: dapm: unexport snd_soc_dapm_init()
Posted by Masahiro Yamada 1 year ago
The symbol provider (sound/soc/soc-dapm.c) and the symbol consumer
(sound/soc/soc-core.c) belong to the same module, snd-soc-core.ko.

There is no need to export it.

Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
---

 sound/soc/soc-dapm.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c
index b5116b700d73..3fa53ce80189 100644
--- a/sound/soc/soc-dapm.c
+++ b/sound/soc/soc-dapm.c
@@ -4865,7 +4865,6 @@ void snd_soc_dapm_init(struct snd_soc_dapm_context *dapm,
 	/* see for_each_card_dapms */
 	list_add(&dapm->list, &card->dapm_list);
 }
-EXPORT_SYMBOL_GPL(snd_soc_dapm_init);
 
 static void soc_dapm_shutdown_dapm(struct snd_soc_dapm_context *dapm)
 {
-- 
2.43.0
Re: [PATCH] ASoC: dapm: unexport snd_soc_dapm_init()
Posted by Mark Brown 1 year ago
On Thu, 06 Feb 2025 01:52:16 +0900, Masahiro Yamada wrote:
> The symbol provider (sound/soc/soc-dapm.c) and the symbol consumer
> (sound/soc/soc-core.c) belong to the same module, snd-soc-core.ko.
> 
> There is no need to export it.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: dapm: unexport snd_soc_dapm_init()
      commit: ecfcee245cc99def0f6bf84ac75ac372f8ab65eb

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