From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932480AbbG1Kjl (ORCPT ); Tue, 28 Jul 2015 06:39:41 -0400 Received: from mail-pa0-f50.google.com ([209.85.220.50]:36682 "EHLO mail-pa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752777AbbG1Kjk (ORCPT ); Tue, 28 Jul 2015 06:39:40 -0400 From: Masanari Iida To: mpe@ellerman.id.au, linux-kernel@vger.kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org Cc: Masanari Iida Subject: [PATCH] Doc: ioctl: Fix typo in botching-up-ioctls.txt Date: Tue, 28 Jul 2015 19:39:47 +0900 Message-Id: <1438079987-22766-1-git-send-email-standby24x7@gmail.com> X-Mailer: git-send-email 2.5.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patch fix typos found in botching-up-ioctls.txt Signed-off-by: Masanari Iida --- Documentation/ioctl/botching-up-ioctls.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/ioctl/botching-up-ioctls.txt b/Documentation/ioctl/botching-up-ioctls.txt index 45fe78c..e3e2de0 100644 --- a/Documentation/ioctl/botching-up-ioctls.txt +++ b/Documentation/ioctl/botching-up-ioctls.txt @@ -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 -- 2.5.0