luck/tmp_suning_uos_patched
1
0
Fork 1
Code Issues Pull Requests Packages Projects Releases Wiki Activity

bcache: update document info

Browse Source 
There is no return in continue_at(), update the documentation.

Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Acked-by: Coly Li <colyli@suse.de>
Signed-off-by: Jens Axboe <axboe@fb.com>
This commit is contained in:
Yijing Wang 2016-07-04 09:23:34 +08:00 committed by Jens Axboe
parent c50d4d5dd3
commit 7abc70d700
2 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
drivers/md/bcache/closure.c
View File

@ -112,7 +112,7 @@ bool closure_wait(struct closure_waitlist *waitlist, struct closure *cl)
EXPORT_SYMBOL(closure_wait); EXPORT_SYMBOL(closure_wait);
/** /**
* closure_sync - sleep until a closure a closure has nothing left to wait on * closure_sync - sleep until a closure has nothing left to wait on
* *
* Sleeps until the refcount hits 1 - the thread that's running the closure owns * Sleeps until the refcount hits 1 - the thread that's running the closure owns
* the last refcount. * the last refcount.

3
drivers/md/bcache/closure.h
View File

@ -31,7 +31,8 @@
* passing it, as you might expect, the function to run when nothing is pending * passing it, as you might expect, the function to run when nothing is pending
* and the workqueue to run that function out of. * and the workqueue to run that function out of.
* *
* continue_at() also, critically, is a macro that returns the calling function. * continue_at() also, critically, requires a 'return' immediately following the
* location where this macro is referenced, to return to the calling function.
* There's good reason for this. * There's good reason for this.
* *
* To use safely closures asynchronously, they must always have a refcount while * To use safely closures asynchronously, they must always have a refcount while