Skip to contentSkip to conversation

ASoC: cs48l32: Fix spelling mistake "exceeeds" -> "exceeds"

PATCH In review Colin Ian King 3 participants 3 messages Apr 16, 2025

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

PATCH 1/1 ASoC: cs48l32: Fix spelling mistake "exceeeds" -> "exceeds"

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

---
 sound/soc/codecs/cs48l32.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/cs48l32.c +1 -1
index 4e2bc09773cb..8fd0df671730 100644
@@ -1802,7 +1802,7 @@ static int cs48l32_fllhj_validate(struct cs48l32_fll *fll,
 	}
 
 	if (fout > CS48L32_FLL_MAX_FOUT) {
-		cs48l32_fll_err(fll, "Fout=%dMHz exceeeds maximum %dMHz\n",
+		cs48l32_fll_err(fll, "Fout=%dMHz exceeds maximum %dMHz\n",
 				fout, CS48L32_FLL_MAX_FOUT);
 		return -EINVAL;
 	}
Signature · 1 line
2.49.0
maintainer Reviewed-by on v1 1/1
#1 lore raw
Quoted 12 lines · Colin Ian King

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

---
  sound/soc/codecs/cs48l32.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/cs48l32.c +0 -0
index 4e2bc09773cb..8fd0df671730 100644

sound/soc/codecs/cs48l32.c static int cs48l32_fllhj_validate(struct cs48l32_fll *fll, · line 1808

Quoted 8 lines
sound/soc/codecs/cs48l32.c +1 -1
@@ -1802,7 +1802,7 @@ static int cs48l32_fllhj_validate(struct cs48l32_fll *fll,
  	}
 
  	if (fout > CS48L32_FLL_MAX_FOUT) {
-		cs48l32_fll_err(fll, "Fout=%dMHz exceeeds maximum %dMHz\n",
+		cs48l32_fll_err(fll, "Fout=%dMHz exceeds maximum %dMHz\n",
  				fout, CS48L32_FLL_MAX_FOUT);
  		return -EINVAL;
  	}
maintainer
#2 lore raw
In reply to Colin Ian King
Quoted 3 lines · Colin Ian King

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

Applied to

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

Thanks!

[1/1] ASoC: cs48l32: Fix spelling mistake "exceeeds" -> "exceeds"

      commit: 7ed50dc550b0a3bad82f675aaefd8cd00362672d

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