linux-kernel - [PATCH] USB: fix typo in documentation

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <eecda72c-33c3-9945-54dc-d51deb515e9a@osg.samsung.com>
Date:   Tue, 1 Nov 2016 15:23:37 +0000
From:   Luis de Bethencourt <luisbg@....samsung.com>
To:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:     corbet@....net, Greg KH <gregkh@...uxfoundation.org>,
        stern@...land.harvard.edu, oneukum@...e.com,
        emilio.lopez@...labora.co.uk, linux-doc@...r.kernel.org
Subject: [PATCH] USB: fix typo in documentation

A typo sneaked in the latest change on the USB documentation. Fixing it
and also a trailing whitespace since it is also in the "USB Host-Side API
Model" chapter.

Signed-off-by: Luis de Bethencourt <luisbg@....samsung.com>
---
 Documentation/DocBook/usb.tmpl | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/DocBook/usb.tmpl b/Documentation/DocBook/usb.tmpl
index 8ec4d59..e322691 100644
--- a/Documentation/DocBook/usb.tmpl
+++ b/Documentation/DocBook/usb.tmpl
@@ -160,7 +160,7 @@
     In theory, all HCDs provide the same functionality through the same
     API.  In practice, that's becoming mostly true,
     but there are still differences that crop up especially with
-    fault handling on the less common controllers.
+    fault handling on the less common controllers.
     Different controllers don't necessarily report
     the same aspects of failures, and recovery from faults (including
     software-induced ones like unlinking an URB) isn't yet fully
@@ -168,7 +168,7 @@
     Device driver authors should make a point of doing disconnect
     testing (while the device is active) with each different host
     controller driver, to make sure drivers don't have bugs of
-    thei1r own as well as to make sure they aren't relying on some
+    their own as well as to make sure they aren't relying on some
     HCD-specific behavior.
     </para>

--
2.8.1