Skip to contentSkip to conversation

Doc: ioctl: Fix typo in botching-up-ioctls.txt

PATCH Applied Masanari Iida 2 participants 2 messages Jul 28, 2015 – Aug 2, 2015 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Doc: ioctl: Fix typo in botching-up-ioctls.txt

This patch fix typos found in botching-up-ioctls.txt

---
 Documentation/ioctl/botching-up-ioctls.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
Documentation/ioctl/botching-up-ioctls.txt +2 -2
index 45fe78c..e3e2de0 100644
@@ -122,7 +122,7 @@ Time, Waiting and Missing it
 ----------------------------
 
 GPUs do most everything asynchronously, so we have a need to time operations and
-wait for oustanding ones. This is really tricky business; at the moment none of
+wait for outstanding ones. This is really tricky business; at the moment none of
 the ioctls supported by the drm/i915 get this fully right, which means there's
 still tons more lessons to learn here.
 
@@ -176,7 +176,7 @@ entails its own little set of pitfalls:
 
  * Ensure that you have sufficient insulation between different clients. By
    default pick a private per-fd namespace which forces any sharing to be done
-   explictly. Only go with a more global per-device namespace if the objects
+   explicitly. Only go with a more global per-device namespace if the objects
    are truly device-unique. One counterexample in the drm modeset interfaces is
    that the per-device modeset objects like connectors share a namespace with
    framebuffer objects, which mostly are not shared at all. A separate
Signature · 1 line
2.5.0
maintainer Applied
#1 lore raw
Quoted 1 line · On Tue, 28 Jul 2015 19:39:47 +0900 Masanari Iida <[email protected]> wrote:

This patch fix typos found in botching-up-ioctls.txt

Applied to the docs tree, thanks.

jon