[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174222863673.227953.6804777136695160780.b4-ty@kernel.org>
Date: Mon, 17 Mar 2025 16:23:56 +0000
From: Mark Brown <broonie@...nel.org>
To: alsa-devel@...a-project.org,
Venkata Prasad Potturu <venkataprasad.potturu@....com>
Cc: Vijendar.Mukunda@....com, mario.limonciello@....com,
Basavaraj.Hiregoudar@....com, Sunil-kumar.Dommati@....com,
syed.sabakareem@....com, nathan@...nel.org,
kernel test robot <lkp@...el.com>, Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.dev>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Jeff Johnson <quic_jjohnson@...cinc.com>,
Greg KH <gregkh@...uxfoundation.org>, Peter Zijlstra <peterz@...radead.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." <linux-sound@...r.kernel.org>
Subject: Re: [PATCH 1/3] ASoC: amd: acp: Fix snd_soc_acpi_mach id's
duplicate symbol error
On Mon, 17 Mar 2025 12:54:07 +0530, Venkata Prasad Potturu wrote:
> Move snd_soc_acpi_mach id's of all acp platforms form header file to
> amd-acpi-mach.c file to avoid below errors.
>
> ld.lld: error: duplicate symbol: amp_rt1019
> ld.lld: error: duplicate symbol: amp_max
> ld.lld: error: duplicate symbol: snd_soc_acpi_amd_acp63_acp_machines
> ld.lld: error: duplicate symbol: snd_soc_acpi_amd_acp70_acp_machines
> ld.lld: error: duplicate symbol: snd_soc_acpi_amd_rmb_acp_machines
> ld.lld: error: duplicate symbol: snd_soc_acpi_amd_acp_machines
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: amd: acp: Fix snd_soc_acpi_mach id's duplicate symbol error
commit: 9c2c0ef6400980f09b377be250f5dff14dbbf3b6
[2/3] ASoC: amd: acp: Fix acp_resource duplicate symbol error
commit: 09dc8031f4a84103f4ba8f704ec21f1926b04366
[3/3] ASoC: amd: acp: Fix acp_common_hw_ops declaration error
commit: 77ad261ecc4aa1b09bc98b32cdbfadb5e92197b7
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