mirror of
https://github.com/torvalds/linux.git
synced 2024-11-10 14:11:52 +00:00
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>
This commit is contained in:
parent
1a695a905c
commit
fac8434dab
@ -6,8 +6,8 @@
|
|||||||
|
|
||||||
This document serves as a guide for device drivers writers on what the
|
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
|
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
|
the fences(struct fence) that are needed to synchronize between drivers or
|
||||||
process boundaries.
|
across process boundaries.
|
||||||
|
|
||||||
The sync_file API is meant to be used to send and receive fence information
|
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
|
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
|
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
|
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
|
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
|
when it has finished using (or processing) that buffer. Out-fences are fences
|
||||||
that the driver creates.
|
that the driver creates.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user