[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <171268903831.71903.8798252407593021756.b4-ty@kernel.org>
Date: Tue, 09 Apr 2024 19:57:18 +0100
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: alsa-devel@...a-project.org, Sunil-kumar.Dommati@....com,
Basavaraj.Hiregoudar@....com, venkataprasad.potturu@....com,
kernel test robot <lkp@...el.com>, Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Arnd Bergmann <arnd@...db.de>, Lucas Tanure <lucas.tanure@...labora.com>,
Cristian Ciocaltea <cristian.ciocaltea@...labora.com>,
Syed Saba Kareem <Syed.SabaKareem@....com>,
"open list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." <linux-sound@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: amd: fix for soundwire build dependencies for
legacy stack
On Mon, 08 Apr 2024 23:32:26 +0530, Vijendar Mukunda wrote:
> The SND_SOC_AMD_SOUNDWIRE Kconfig symbol has build dependency on
> SOUNDWIRE_AMD. It gets it wrong for a configuration involving
> SND_SOC_AMD_SOUNDWIRE_LINK_BASELINE=y,SND_SOC_AMD_PS=y and SOUNDWIRE_AMD=m,
> which results in a link failure:
>
> ld: vmlinux.o: in function `amd_sdw_probe':
> >> sound/soc/amd/ps/pci-ps.c:271:(.text+0x1d51eff):
> undefined reference to `sdw_amd_probe'
> ld: vmlinux.o: in function `acp63_sdw_machine_select':
> >> sound/soc/amd/ps/pci-ps.c:294:(.text+0x1d525d5):
> undefined reference to `sdw_amd_get_slave_info'
> ld: vmlinux.o: in function `amd_sdw_exit':
> >> sound/soc/amd/ps/pci-ps.c:280:(.text+0x1d538ce):
> undefined reference to `sdw_amd_exit'
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: amd: fix for soundwire build dependencies for legacy stack
commit: 56437a561fefab2be708dfebf80e31c4715eb52e
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
Powered by blists - more mailing lists