Skip to contentSkip to conversation

ASoC: remove zte zx dangling kconfig

PATCH In review Peter Robinson 3 participants 3 messages Jun 27, 2021 – Jun 28, 2021

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

PATCH v2 1/1 ASoC: remove zte zx dangling kconfig

In commit dc98f1d we removed the zte zx sound drivers but there was a dangling Kconfig left around for the codec so fix this.

Fixes dc98f1d655ca ("ASoC: remove zte zx drivers")
Cc Arnd Bergmann <[email protected]>
Cc Mark Brown <[email protected]>

---

v2 - fix the Fixes line

 sound/soc/codecs/Kconfig | 5 -----
 1 file changed, 5 deletions(-)
sound/soc/codecs/Kconfig +0 -5
index 1c87b42606c9..e04fa8b5f178 100644
@@ -1739,11 +1739,6 @@ config SND_SOC_ZL38060
 	  which consists of a Digital Signal Processor (DSP), several Digital
 	  Audio Interfaces (DAIs), analog outputs, and a block of 14 GPIOs.
 
-config SND_SOC_ZX_AUD96P22
-	tristate "ZTE ZX AUD96P22 CODEC"
-	depends on I2C
-	select REGMAP_I2C
-
 # Amp
 config SND_SOC_LM4857
 	tristate
Signature · 1 line
2.31.1
maintainer
#2 lore raw
In reply to Peter Robinson
Quoted 2 lines · Peter Robinson

In commit dc98f1d we removed the zte zx sound drivers but there was a dangling Kconfig left around for the codec so fix this.

Applied to

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

Thanks!

[1/1] ASoC: remove zte zx dangling kconfig

      commit: 0c4f8fd3ed9cb27228497f0ae495ea6cef7017b1

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