Commit c240a714 authored by Gustavo Padovan's avatar Gustavo Padovan Committed by Greg Kroah-Hartman

staging/android: improve documentation for sync_file

num_fences was missing a colon mark and sync_file_create() now have
better description.
Signed-off-by: default avatarGustavo Padovan <gustavo.padovan@collabora.co.uk>
Reviewed-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent d4cab38e
...@@ -65,11 +65,12 @@ static void fence_check_cb_func(struct fence *f, struct fence_cb *cb) ...@@ -65,11 +65,12 @@ static void fence_check_cb_func(struct fence *f, struct fence_cb *cb)
} }
/** /**
* sync_fence_create() - creates a sync fence * sync_file_create() - creates a sync file
* @fence: fence to add to the sync_fence * @fence: fence to add to the sync_fence
* *
* Creates a sync_file containg @fence. Once this is called, the sync_file * Creates a sync_file containg @fence. Once this is called, the sync_file
* takes ownership of @fence. * takes ownership of @fence. The sync_file can be released with
* fput(sync_file->file). Returns the sync_file or NULL in case of error.
*/ */
struct sync_file *sync_file_create(struct fence *fence) struct sync_file *sync_file_create(struct fence *fence)
{ {
......
...@@ -32,7 +32,7 @@ struct sync_file_cb { ...@@ -32,7 +32,7 @@ struct sync_file_cb {
* @kref: reference count on fence. * @kref: reference count on fence.
* @name: name of sync_file. Useful for debugging * @name: name of sync_file. Useful for debugging
* @sync_file_list: membership in global file list * @sync_file_list: membership in global file list
* @num_fences number of sync_pts in the fence * @num_fences: number of sync_pts in the fence
* @wq: wait queue for fence signaling * @wq: wait queue for fence signaling
* @status: 0: signaled, >0:active, <0: error * @status: 0: signaled, >0:active, <0: error
* @cbs: sync_pts callback information * @cbs: sync_pts callback information
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment