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

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

[Randy Dunlap]

From: Randy Dunlap <rdunlap@infradead.org>

Change doubled word "be" to "to be".

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

--- linux-next-20200714.orig/include/linux/regmap.h
+++ linux-next-20200714/include/linux/regmap.h
@@ -275,7 +275,7 @@ typedef void (*regmap_unlock)(void *);
  *			readable if it belongs to one of the ranges specified
  *			by rd_noinc_table).
  * @disable_locking: This regmap is either protected by external means or
- *                   is guaranteed not be be accessed from multiple threads.
+ *                   is guaranteed not to be accessed from multiple threads.
  *                   Don't use any locking mechanisms.
  * @lock:	  Optional lock callback (overrides regmap's default lock
  *		  function, based on spinlock or mutex).

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

[Mark Brown]

On Wed, 15 Jul 2020 18:30:12 -0700, Randy Dunlap wrote:
> Change doubled word "be" to "to be".

Applied to

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

Thanks!

[1/1] regmap: fix duplicated word in <linux/regmap.h>
      commit: 6611561a7a7ef925294353a4c2124bdb66eb831c

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