Skip to contentSkip to conversation

ASoC: pxa: remove duplicated CONFIG_SND_PXA2XX_AC97 entry

PATCH In review Masahiro Yamada 2 participants 2 messages Feb 4, 2024 – Feb 6, 2024

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 ASoC: pxa: remove duplicated CONFIG_SND_PXA2XX_AC97 entry

'config SND_PXA2XX_AC97' is already present in sound/arm/Kconfig with a prompt.

Commit 734c2d4bb7cf ("[ALSA] ASoC pxa2xx build support") redundantly added the second one to sound/soc/pxa/Kconfig.

Remove it.

---

Changes in v2:
- Change the commit subject

 sound/soc/pxa/Kconfig | 3 ---
 1 file changed, 3 deletions(-)
sound/soc/pxa/Kconfig +0 -3
index f03c74809324..e05d6ce4c8fa 100644
@@ -8,9 +8,6 @@ config SND_PXA2XX_SOC
 	  the PXA2xx AC97, I2S or SSP interface. You will also need
 	  to select the audio interfaces to support below.
 
-config SND_PXA2XX_AC97
-	tristate
-
 config SND_PXA2XX_SOC_AC97
 	tristate "SoC AC97 support for PXA2xx"
 	depends on SND_PXA2XX_SOC
Signature · 1 line
2.40.1
maintainer
#1 lore raw
Quoted 9 lines · Masahiro Yamada

'config SND_PXA2XX_AC97' is already present in sound/arm/Kconfig with a prompt.

Commit 734c2d4bb7cf ("[ALSA] ASoC pxa2xx build support") redundantly added the second one to sound/soc/pxa/Kconfig.

Remove it.

[...]

Applied to

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

Thanks!

[1/1] ASoC: pxa: remove duplicated CONFIG_SND_PXA2XX_AC97 entry

      commit: 8f501d29c7a6a03303c1a085fd27948e1edb0c90

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