Fix typo in "communicate directly with with the pinctrl subsystem".
Signed-off-by: James Hogan <[email protected]>
Cc: Linus Walleij <[email protected]>
Cc: Rob Landley <[email protected]>
---
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
On Tue, May 28, 2013 at 11:31 AM, James Hogan <[email protected]> wrote:
> Fix typo in "communicate directly with with the pinctrl subsystem".
>
> Signed-off-by: James Hogan <[email protected]>
> Cc: Linus Walleij <[email protected]>
> Cc: Rob Landley <[email protected]>
Patch applied!
Thanks,
Linus Walleij
On 05/28/2013 04:31:48 AM, James Hogan wrote:
> Fix typo in "communicate directly with with the pinctrl subsystem".
>
> Signed-off-by: James Hogan <[email protected]>
> Cc: Linus Walleij <[email protected]>
> Cc: Rob Landley <[email protected]>
Acked-by: Rob Landley <[email protected]>
Please send to [email protected].
Rob-