[PATCH][next] ASoC: tas2781: Fix spelling mistake "calibraiton" -> "calibration"

[PATCH][next] ASoC: tas2781: Fix spelling mistake "calibraiton" -> "calibration"

[Colin Ian King]

There is a spelling mistake in a dev_err message. Fix it. Also fix
grammar and add space between last word and (%d)".

Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
 sound/soc/codecs/tas2781-fmwlib.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/soc/codecs/tas2781-fmwlib.c b/sound/soc/codecs/tas2781-fmwlib.c
index 432b19ccec8c..cbf0aef2c001 100644
--- a/sound/soc/codecs/tas2781-fmwlib.c
+++ b/sound/soc/codecs/tas2781-fmwlib.c
@@ -1863,7 +1863,7 @@ static int fw_parse_calibration_data(struct tasdevice_priv *tas_priv,
 
 	if (tas_fmw->nr_calibrations != 1) {
 		dev_err(tas_priv->dev,
-			"%s: only support one calibraiton(%d)!\n",
+			"%s: only supports one calibration (%d)!\n",
 			__func__, tas_fmw->nr_calibrations);
 		goto out;
 	}
-- 
2.39.2

Re: [PATCH][next] ASoC: tas2781: Fix spelling mistake "calibraiton" -> "calibration"

[Mark Brown]

On Tue, 20 Jun 2023 10:56:20 +0100, Colin Ian King wrote:
> There is a spelling mistake in a dev_err message. Fix it. Also fix
> grammar and add space between last word and (%d)".
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: tas2781: Fix spelling mistake "calibraiton" -> "calibration"
      commit: 0a08778126284481c300336f1ba3d7b1906851a5

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