[PATCH] spi: fix duplicated word in <linux/spi/spi.h>

[PATCH] spi: fix duplicated word in <linux/spi/spi.h>

[Randy Dunlap]

From: Randy Dunlap <rdunlap@infradead.org>

Change doubled word "as" to "as a".

Change "Return: Return:" in kernel-doc notation to have only one
"Return:".

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org
---
 include/linux/spi/spi.h |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- linux-next-20200714.orig/include/linux/spi/spi.h
+++ linux-next-20200714/include/linux/spi/spi.h
@@ -971,7 +971,7 @@ struct spi_transfer {
  * each represented by a struct spi_transfer.  The sequence is "atomic"
  * in the sense that no other spi_message may use that SPI bus until that
  * sequence completes.  On some systems, many such sequences can execute as
- * as single programmed DMA transfer.  On all systems, these messages are
+ * a single programmed DMA transfer.  On all systems, these messages are
  * queued, and might complete after transactions to other devices.  Messages
  * sent to a given spi_device are always executed in FIFO order.
  *
@@ -1234,7 +1234,7 @@ extern int spi_bus_unlock(struct spi_con
  *
  * For more specific semantics see spi_sync().
  *
- * Return: Return: zero on success, else a negative error code.
+ * Return: zero on success, else a negative error code.
  */
 static inline int
 spi_sync_transfer(struct spi_device *spi, struct spi_transfer *xfers,

Re: [PATCH] spi: fix duplicated word in <linux/spi/spi.h>

[Mark Brown]

On Wed, 15 Jul 2020 18:30:48 -0700, Randy Dunlap wrote:
> Change doubled word "as" to "as a".
> 
> Change "Return: Return:" in kernel-doc notation to have only one
> "Return:".

Applied to

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

Thanks!

[1/1] spi: fix duplicated word in <linux/spi/spi.h>
      commit: 2ae3de10abfe0be40c9d93ebc2f429b969abf008

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