[PATCH][next] spi: hisi-sfc-v3xx: fix spelling mistake "occured" -> "occurred"

[PATCH][next] spi: hisi-sfc-v3xx: fix spelling mistake "occured" -> "occurred"

[Colin King]

From: Colin Ian King <colin.king@canonical.com>

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

Signed-off-by: Colin Ian King <colin.king@canonical.com>
---
 drivers/spi/spi-hisi-sfc-v3xx.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/spi/spi-hisi-sfc-v3xx.c b/drivers/spi/spi-hisi-sfc-v3xx.c
index 46454dc2d109..4650b483a33d 100644
--- a/drivers/spi/spi-hisi-sfc-v3xx.c
+++ b/drivers/spi/spi-hisi-sfc-v3xx.c
@@ -121,7 +121,7 @@ static int hisi_sfc_v3xx_handle_completion(struct hisi_sfc_v3xx_host *host)
 	 * happens, we regard it as an unsupported error here.
 	 */
 	if (!(reg & HISI_SFC_V3XX_INT_MASK_CPLT)) {
-		dev_err(host->dev, "unsupported error occured, status=0x%x\n", reg);
+		dev_err(host->dev, "unsupported error occurred, status=0x%x\n", reg);
 		return -EIO;
 	}
 
-- 
2.27.0

Re: [PATCH][next] spi: hisi-sfc-v3xx: fix spelling mistake "occured" -> "occurred"

[Mark Brown]

On Mon, 28 Sep 2020 13:30:42 +0100, Colin 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/spi.git for-next

Thanks!

[1/1] spi: hisi-sfc-v3xx: fix spelling mistake "occured" -> "occurred"
      commit: 0e9683659c6926fd3f30345f9f58893e630379ed

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