bcache: update document info
authorYijing Wang <wangyijing@huawei.com>
Mon, 4 Jul 2016 01:23:34 +0000 (09:23 +0800)
committerJens Axboe <axboe@fb.com>
Tue, 5 Jul 2016 17:34:49 +0000 (11:34 -0600)
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>
drivers/md/bcache/closure.c
drivers/md/bcache/closure.h

index 9eaf1d6e83023a2045063b8761a89b3983952f7c..864e673aec39598d2f7f99e43c5b3168f2c1d736 100644 (file)
@@ -112,7 +112,7 @@ bool closure_wait(struct closure_waitlist *waitlist, struct closure *cl)
 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
  * the last refcount.
index 782cc2c8a1853d1c33c297961ccabf7a7683bc49..9b2fe2d3e3a941755bec117e880b665c32905c02 100644 (file)
@@ -31,7 +31,8 @@
  * passing it, as you might expect, the function to run when nothing is pending
  * 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.
  *
  * To use safely closures asynchronously, they must always have a refcount while