linux-kernel - Re: [PATCH] ASoC: Intel: fix SND_SOC

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]

Message-Id: <175248920349.18169.8570920446086956809.b4-ty@kernel.org>
Date: Mon, 14 Jul 2025 11:33:23 +0100
From: Mark Brown <broonie@...nel.org>
To: Cezary Rojewski <cezary.rojewski@...el.com>, 
 Liam Girdwood <liam.r.girdwood@...ux.intel.com>, 
 Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>, 
 Bard Liao <yung-chuan.liao@...ux.intel.com>, 
 Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>, 
 Kai Vehmanen <kai.vehmanen@...ux.intel.com>, 
 Arnd Bergmann <arnd@...nel.org>
Cc: Arnd Bergmann <arnd@...db.de>, 
 Pierre-Louis Bossart <pierre-louis.bossart@...ux.dev>, 
 Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
 Brent Lu <brent.lu@...el.com>, Vijendar Mukunda <Vijendar.Mukunda@....com>, 
 Jack Yu <jack.yu@...ltek.com>, Helen Koike <koike@...lia.com>, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: Intel: fix SND_SOC_SOF dependencies

On Wed, 09 Jul 2025 16:56:07 +0200, Arnd Bergmann wrote:
> It is currently possible to configure a kernel with all Intel SoC
> configs as loadable modules, but the board config as built-in. This
> causes a link failure in the reference to the snd_soc_sof.ko module:
> 
> x86_64-linux-ld: sound/soc/intel/boards/sof_rt5682.o: in function `sof_rt5682_hw_params':
> sof_rt5682.c:(.text+0x1f9): undefined reference to `sof_dai_get_mclk'
> x86_64-linux-ld: sof_rt5682.c:(.text+0x234): undefined reference to `sof_dai_get_bclk'
> x86_64-linux-ld: sound/soc/intel/boards/sof_rt5682.o: in function `sof_rt5682_codec_init':
> sof_rt5682.c:(.text+0x3e0): undefined reference to `sof_dai_get_mclk'
> x86_64-linux-ld: sound/soc/intel/boards/sof_cs42l42.o: in function `sof_cs42l42_hw_params':
> sof_cs42l42.c:(.text+0x2a): undefined reference to `sof_dai_get_bclk'
> x86_64-linux-ld: sound/soc/intel/boards/sof_nau8825.o: in function `sof_nau8825_hw_params':
> sof_nau8825.c:(.text+0x7f): undefined reference to `sof_dai_get_bclk'
> x86_64-linux-ld: sound/soc/intel/boards/sof_da7219.o: in function `da7219_codec_init':
> sof_da7219.c:(.text+0xbf): undefined reference to `sof_dai_get_mclk'
> x86_64-linux-ld: sound/soc/intel/boards/sof_maxim_common.o: in function `max_98373_hw_params':
> sof_maxim_common.c:(.text+0x6f9): undefined reference to `sof_dai_get_tdm_slots'
> x86_64-linux-ld: sound/soc/intel/boards/sof_realtek_common.o: in function `rt1015_hw_params':
> sof_realtek_common.c:(.text+0x54c): undefined reference to `sof_dai_get_bclk'
> x86_64-linux-ld: sound/soc/intel/boards/sof_realtek_common.o: in function `rt1308_hw_params':
> sof_realtek_common.c:(.text+0x702): undefined reference to `sof_dai_get_mclk'
> x86_64-linux-ld: sound/soc/intel/boards/sof_cirrus_common.o: in function `cs35l41_hw_params':
> sof_cirrus_common.c:(.text+0x2f): undefined reference to `sof_dai_get_bclk'
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: Intel: fix SND_SOC_SOF dependencies
      commit: e837b59f8b411b5baf5e3de7a5aea10b1c545a63

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