diff options
author | Javier Martinez Canillas <javier@osg.samsung.com> | 2016-05-14 02:28:36 -0400 |
---|---|---|
committer | Jonathan Corbet <corbet@lwn.net> | 2016-06-03 13:24:16 -0600 |
commit | fac8434dab9645905d0f1f6baaa0f2e27daca435 (patch) | |
tree | 37b9918663370466c9a2fa5aaedec1a222bf16d3 /Documentation | |
parent | 1a695a905c18548062509178b98bc91e67510864 (diff) | |
download | linux-fac8434dab9645905d0f1f6baaa0f2e27daca435.tar.bz2 |
Documentation: Fix some grammar mistakes in sync_file.txt
There are two sentences in the Sync File documentation where the
english is a little off. This patch is an attempt to fix these.
Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
Reviewed-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/sync_file.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/sync_file.txt b/Documentation/sync_file.txt index eaf8297dbca2..e8e2ebafe5fa 100644 --- a/Documentation/sync_file.txt +++ b/Documentation/sync_file.txt @@ -6,8 +6,8 @@ This document serves as a guide for device drivers writers on what the sync_file API is, and how drivers can support it. Sync file is the carrier of -the fences(struct fence) that needs to synchronized between drivers or across -process boundaries. +the fences(struct fence) that are needed to synchronize between drivers or +across process boundaries. The sync_file API is meant to be used to send and receive fence information to/from userspace. It enables userspace to do explicit fencing, where instead @@ -32,7 +32,7 @@ in-fences and out-fences Sync files can go either to or from userspace. When a sync_file is sent from the driver to userspace we call the fences it contains 'out-fences'. They are related to a buffer that the driver is processing or is going to process, so -the driver an create out-fence to be able to notify, through fence_signal(), +the driver creates an out-fence to be able to notify, through fence_signal(), when it has finished using (or processing) that buffer. Out-fences are fences that the driver creates. |