| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1369733508-21392-1-git-send-email-james.hogan@imgtec.com> Date: Tue, 28 May 2013 10:31:48 +0100 From: James Hogan <james.hogan@...tec.com> To: Linus Walleij <linus.walleij@...aro.org> CC: <linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>, James Hogan <james.hogan@...tec.com>, Rob Landley <rob@...dley.net> Subject: [PATCH] Documentation/pinctrl.txt: fix typo "with with" Fix typo in "communicate directly with with the pinctrl subsystem". Signed-off-by: James Hogan <james.hogan@...tec.com> Cc: Linus Walleij <linus.walleij@...aro.org> Cc: Rob Landley <rob@...dley.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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists