Skip to contentSkip to conversation

spi: cadence: Fix spelling mistake "nunber" -> "number"

PATCH In review Colin King 3 participants 3 messages Sep 28, 2021

Subsystems (2)
lore
Share & tools
lore

Colin King

author
#0 lore raw

PATCH 1/1 spi: cadence: Fix spelling mistake "nunber" -> "number"

From: Colin Ian King <[email protected]>

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

---
 drivers/spi/spi-cadence-xspi.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/spi/spi-cadence-xspi.c +1 -1
index a2a94675292d..3401fcf49f4a 100644
@@ -308,7 +308,7 @@ static int cdns_xspi_controller_init(struct cdns_xspi_dev *cdns_xspi)
 	hw_magic_num = FIELD_GET(CDNS_XSPI_MAGIC_NUM, ctrl_ver);
 	if (hw_magic_num != CDNS_XSPI_MAGIC_NUM_VALUE) {
 		dev_err(cdns_xspi->dev,
-			"Incorrect XSPI magic nunber: %x, expected: %x\n",
+			"Incorrect XSPI magic number: %x, expected: %x\n",
 			hw_magic_num, CDNS_XSPI_MAGIC_NUM_VALUE);
 		return -EIO;
 	}
Signature · 1 line
2.32.0
maintainer
#2 lore raw
In reply to Colin King
Quoted 5 lines · Colin King

From: Colin Ian King <[email protected]>

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

Applied to

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

Thanks!

[1/1] spi: cadence: Fix spelling mistake "nunber" -> "number"

      commit: 5c258a8a9cf987b254c4ebdb6481a4d76bcf490b

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