Skip to contentSkip to conversation

ASoC: atmel: mchp-pdmc: Fix spelling mistake "microchopnes" -> "microphones"

PATCH In review Colin Ian King 3 participants 3 messages Mar 9, 2022 – Mar 10, 2022

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

PATCH 1/1 ASoC: atmel: mchp-pdmc: Fix spelling mistake "microchopnes" -> "microphones"

There is a spelling mistake in a dev_info message. Fix it.

---
 sound/soc/atmel/mchp-pdmc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/atmel/mchp-pdmc.c +1 -1
index c44636f6207d..871834fb9b77 100644
@@ -892,7 +892,7 @@ static int mchp_pdmc_dt_init(struct mchp_pdmc *dd)
 
 	dd->mic_no /= 2;
 
-	dev_info(dd->dev, "%d PDM microchopnes declared\n", dd->mic_no);
+	dev_info(dd->dev, "%d PDM microphones declared\n", dd->mic_no);
 
 	/* by default, we consider the order of microphones in mchp,mic-pos to
 	 * be the same with the channel mapping; 1st microphone channel 0, 2nd
Signature · 1 line
2.35.1
maintainer
#2 lore raw
In reply to Colin Ian King
Quoted 3 lines · Colin Ian King

There is a spelling mistake in a dev_info message. Fix it.

Applied to

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

Thanks!

[1/1] ASoC: atmel: mchp-pdmc: Fix spelling mistake "microchopnes" -> "microphones"

      commit: 6b6bb5e26222021abe1c5360f43b4c2ff1dd012f

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