summaryrefslogtreecommitdiffstats
path: root/Documentation/sync_file.txt
diff options
context:
space:
mode:
authorTamara Diaconita <diaconitatamara@gmail.com>2017-03-16 17:39:46 +0200
committerJonathan Corbet <corbet@lwn.net>2017-03-17 13:03:36 -0600
commit7bc41a655db9b9e7ba195b27f9070ec957a89816 (patch)
tree86f1faac9b05efa7840888ab41066cf9f94afcbe /Documentation/sync_file.txt
parentf8998c226587fba2faa1f2dfff231b2b1af9a229 (diff)
downloadlinux-0-day-7bc41a655db9b9e7ba195b27f9070ec957a89816.tar.gz
linux-0-day-7bc41a655db9b9e7ba195b27f9070ec957a89816.tar.xz
Documentation: sync_file.txt: Fix typos
Fix spelling mistakes in sync_file.txt to make documentation clear. Signed-off-by: Tamara Diaconita <diaconita.tamara@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/sync_file.txt')
-rw-r--r--Documentation/sync_file.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/sync_file.txt b/Documentation/sync_file.txt
index 269681a6faec8..c3d033a06e8d2 100644
--- a/Documentation/sync_file.txt
+++ b/Documentation/sync_file.txt
@@ -37,7 +37,7 @@ dma_fence_signal(), when it has finished using (or processing) that buffer.
Out-fences are fences that the driver creates.
On the other hand if the driver receives fence(s) through a sync_file from
-userspace we call these fence(s) 'in-fences'. Receiveing in-fences means that
+userspace we call these fence(s) 'in-fences'. Receiving in-fences means that
we need to wait for the fence(s) to signal before using any buffer related to
the in-fences.