Skip to contentSkip to conversation

ASoC: SMA1303: Fix spelling mistake "Invald" -> "Invalid"

PATCH In review Colin Ian King 2 participants 2 messages Jan 30, 2023

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

PATCH 1/1 ASoC: SMA1303: Fix spelling mistake "Invald" -> "Invalid"

There are spelling mistakes in dev_err messages. Fix them.

---
 sound/soc/codecs/sma1303.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
sound/soc/codecs/sma1303.c +2 -2
index d3ee831e88f0..3d8e3900f5c3 100644
@@ -500,7 +500,7 @@ static int sma1303_aif_in_event(struct snd_soc_dapm_widget *w,
 			sma1303->amp_mode = SMA1303_STEREO;
 			break;
 		default:
-			dev_err(sma1303->dev, "%s : Invald value (%d)\n",
+			dev_err(sma1303->dev, "%s : Invalid value (%d)\n",
 								__func__, mux);
 			return -EINVAL;
 		}
@@ -640,7 +640,7 @@ static int sma1303_aif_out_event(struct snd_soc_dapm_widget *w,
 				change = true;
 			break;
 		default:
-			dev_err(sma1303->dev, "%s : Invald value (%d)\n",
+			dev_err(sma1303->dev, "%s : Invalid value (%d)\n",
 								__func__, mux);
 			return -EINVAL;
 		}
Signature · 1 line
2.30.2
maintainer
#1 lore raw
Quoted 3 lines · Colin Ian King

There are spelling mistakes in dev_err messages. Fix them.

Applied to

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

Thanks!

[1/1] ASoC: SMA1303: Fix spelling mistake "Invald" -> "Invalid"

      commit: 5b28c049ff53cf49e3a97d80cebd2e9c2779ea96

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