[PATCH] spi: Kconfig: fix a spelling mistake & hyphenation

Randy Dunlap posted 1 patch 2 years, 7 months ago
drivers/spi/Kconfig |    2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[PATCH] spi: Kconfig: fix a spelling mistake & hyphenation
Posted by Randy Dunlap 2 years, 7 months ago
Correct a spelling mistake (reported by codespell).
Also hyphenate "8-bit".

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org
---
 drivers/spi/Kconfig |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff -- a/drivers/spi/Kconfig b/drivers/spi/Kconfig
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfig
@@ -247,7 +247,7 @@ config SPI_CADENCE_XSPI
 	  Enable support for the Cadence XSPI Flash controller.
 
 	  Cadence XSPI is a specialized controller for connecting an SPI
-	  Flash over upto 8bit wide bus. Enable this option if you have a
+	  Flash over up to 8-bit wide bus. Enable this option if you have a
 	  device with a Cadence XSPI controller and want to access the
 	  Flash as an MTD device.
Re: [PATCH] spi: Kconfig: fix a spelling mistake & hyphenation
Posted by Mark Brown 2 years, 7 months ago
On Tue, 24 Jan 2023 15:35:02 -0800, Randy Dunlap wrote:
> Correct a spelling mistake (reported by codespell).
> Also hyphenate "8-bit".
> 
> 

Applied to

   broonie/spi.git for-next

Thanks!

[1/1] spi: Kconfig: fix a spelling mistake & hyphenation
      commit: 22913a63b477c5f167012d4f1265d023a102c1fe

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