Skip to contentSkip to conversation

ASoC: tlv320aic31xx: Fix typos

PATCH In review Andrew Kreimer 2 participants 4 messages Sep 10, 2024 – Sep 11, 2024

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

PATCH 1/1 ASoC: tlv320aic31xx: Fix typos

Fix typos in comments.

---
 sound/soc/codecs/tlv320aic31xx.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/tlv320aic31xx.c +1 -1
index 7e624c4b77b6..187d68e8688c 100644
@@ -895,7 +895,7 @@ static int aic31xx_setup_pll(struct snd_soc_component *component,
 		dev_err(component->dev,
 			"%s: Sample rate (%u) and format not supported\n",
 			__func__, params_rate(params));
-		/* See bellow for details how fix this. */
+		/* See below for details on how to fix this. */
 		return -EINVAL;
 	}
 	if (bclk_score != 0) {
Signature · 1 line
2.46.0
maintainer
#1 lore raw

sound/soc/codecs/tlv320aic31xx.c static int aic31xx_setup_pll(struct snd_soc_component *component, · line 899

Quoted 3 lines · Andrew Kreimer
sound/soc/codecs/tlv320aic31xx.c +1 -1
-		/* See bellow for details how fix this. */
+		/* See below for details on how to fix this. */
 		return -EINVAL;

This is audio, bellowing seems entirely appropriate!

#2 lore raw
Quoted 7 lines · Mark Brown

sound/soc/codecs/tlv320aic31xx.c static int aic31xx_setup_pll(struct snd_soc_component *component, · line 899

Quoted 3 lines · Andrew Kreimer
sound/soc/codecs/tlv320aic31xx.c +1 -1
-		/* See bellow for details how fix this. */
+		/* See below for details on how to fix this. */
 		return -EINVAL;

This is audio, bellowing seems entirely appropriate!

My bad!

maintainer
#3 lore raw
In reply to Andrew Kreimer
Quoted 3 lines · Andrew Kreimer

Fix typos in comments.

Applied to

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

Thanks!

[1/1] ASoC: tlv320aic31xx: Fix typos

      commit: 69f3014248f0f10e24f07a66ae650061ecaf732b

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