public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] Documentation/pinctrl.txt: fix typo "with with"
@ 2013-05-28  9:31 James Hogan
  2013-05-28 21:28 ` Rob Landley
  2013-05-29 15:50 ` Linus Walleij
  0 siblings, 2 replies; 3+ messages in thread
From: James Hogan @ 2013-05-28  9:31 UTC (permalink / raw)
  To: Linus Walleij; +Cc: linux-doc, linux-kernel, James Hogan, Rob Landley

Fix typo in "communicate directly with with the pinctrl subsystem".

Signed-off-by: James Hogan <james.hogan@imgtec.com>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Rob Landley <rob@landley.net>
---
 Documentation/pinctrl.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt
index 447fd4c..f6e664b 100644
--- a/Documentation/pinctrl.txt
+++ b/Documentation/pinctrl.txt
@@ -1226,8 +1226,8 @@ setting up the config and muxing for the pins right before the device is
 probing, nevertheless orthogonal to the GPIO subsystem.
 
 But there are also situations where it makes sense for the GPIO subsystem
-to communicate directly with with the pinctrl subsystem, using the latter
-as a back-end. This is when the GPIO driver may call out to the functions
+to communicate directly with the pinctrl subsystem, using the latter as a
+back-end. This is when the GPIO driver may call out to the functions
 described in the section "Pin control interaction with the GPIO subsystem"
 above. This only involves per-pin multiplexing, and will be completely
 hidden behind the gpio_*() function namespace. In this case, the driver
-- 
1.8.1.2



^ permalink raw reply related	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-05-30  4:05 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-28  9:31 [PATCH] Documentation/pinctrl.txt: fix typo "with with" James Hogan
2013-05-28 21:28 ` Rob Landley
2013-05-29 15:50 ` Linus Walleij

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox