diff options
| author | Tamara Diaconita <diaconitatamara@gmail.com> | 2017-03-16 16:39:46 +0100 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2017-03-17 20:03:36 +0100 |
| commit | 7bc41a655db9b9e7ba195b27f9070ec957a89816 (patch) | |
| tree | 86f1faac9b05efa7840888ab41066cf9f94afcbe /Documentation | |
| parent | lib/Kconfig.debug: correct documentation paths (diff) | |
| download | linux-7bc41a655db9b9e7ba195b27f9070ec957a89816.tar.xz linux-7bc41a655db9b9e7ba195b27f9070ec957a89816.zip | |
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')
| -rw-r--r-- | Documentation/sync_file.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/sync_file.txt b/Documentation/sync_file.txt index 269681a6faec..c3d033a06e8d 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. |