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

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

diff --git a/sound/soc/ti/omap-dmic.c b/sound/soc/ti/omap-dmic.c
index a26588e9c3bc..f3eed20611a3 100644
--- a/sound/soc/ti/omap-dmic.c
+++ b/sound/soc/ti/omap-dmic.c
@@ -474,7 +474,7 @@ static int asoc_dmic_probe(struct platform_device *pdev)
 
 	dmic->fclk = devm_clk_get(dmic->dev, "fck");
 	if (IS_ERR(dmic->fclk)) {
-		dev_err(dmic->dev, "cant get fck\n");
+		dev_err(dmic->dev, "can't get fck\n");
 		return -ENODEV;
 	}
 
-- 
2.35.1

On 16/03/2022 01:08, Colin Ian King wrote:
> There is a spelling mistake in a dev_err message. Fix it.

Acked-by: Peter Ujfalusi <peter.ujfalusi@gmail.com>

> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
>  sound/soc/ti/omap-dmic.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/sound/soc/ti/omap-dmic.c b/sound/soc/ti/omap-dmic.c
> index a26588e9c3bc..f3eed20611a3 100644
> --- a/sound/soc/ti/omap-dmic.c
> +++ b/sound/soc/ti/omap-dmic.c
> @@ -474,7 +474,7 @@ static int asoc_dmic_probe(struct platform_device *pdev)
>  
>  	dmic->fclk = devm_clk_get(dmic->dev, "fck");
>  	if (IS_ERR(dmic->fclk)) {
> -		dev_err(dmic->dev, "cant get fck\n");
> +		dev_err(dmic->dev, "can't get fck\n");
>  		return -ENODEV;
>  	}
>  

-- 
Péter

On Wed, Mar 16, 2022 at 08:34:12AM +0200, Péter Ujfalusi wrote:
> 
> 
> On 16/03/2022 01:08, Colin Ian King wrote:
> > There is a spelling mistake in a dev_err message. Fix it.
> 
> Acked-by: Peter Ujfalusi <peter.ujfalusi@gmail.com>
>
Acked-by: Jarkko Nikula <jarkko.nikula@bitmer.com>

On Tue, 15 Mar 2022 23:08:16 +0000, Colin Ian King wrote:
> There is a spelling mistake in a dev_err message. Fix it.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: ti: Fix spelling mistake "cant" -> "can't"
      commit: e8ca4cee43fa9d841d25c2b98c9c3a3390593094

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