diff options
author | Yijing Wang <wangyijing@huawei.com> | 2016-07-04 09:23:34 +0800 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2016-07-05 11:34:49 -0600 |
commit | 7abc70d7007757ac1c0e87c57f39cd79f50a632f (patch) | |
tree | e9509e76c2f0056c10fb3c8eed5f7aef71e668cb /drivers/md/bcache/closure.h | |
parent | c50d4d5dd367f996393f1d33f5a3a3048bb414f8 (diff) | |
download | linux-7abc70d7007757ac1c0e87c57f39cd79f50a632f.tar.bz2 |
bcache: update document info
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>
Diffstat (limited to 'drivers/md/bcache/closure.h')
-rw-r--r-- | drivers/md/bcache/closure.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/md/bcache/closure.h b/drivers/md/bcache/closure.h index 782cc2c8a185..9b2fe2d3e3a9 100644 --- a/drivers/md/bcache/closure.h +++ b/drivers/md/bcache/closure.h @@ -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 |