summaryrefslogtreecommitdiff
path: root/drivers/md/dm-bufio.h
diff options
context:
space:
mode:
authorWolfram Sang <wsa@the-dreams.de>2013-11-14 14:32:01 -0800
committerHyungwon Hwang <human.hwang@samsung.com>2014-12-17 16:18:03 +0900
commit1e468171bc4d7b4b159a7d65245c8de07f4537d3 (patch)
tree6244c6361e4e83d821d12f4b2c5054c05a47bb9b /drivers/md/dm-bufio.h
parentf75fed14d002a0b501c9ef8db24ed80f3c046e52 (diff)
downloadlinux-3.10-1e468171bc4d7b4b159a7d65245c8de07f4537d3.tar.gz
linux-3.10-1e468171bc4d7b4b159a7d65245c8de07f4537d3.tar.bz2
linux-3.10-1e468171bc4d7b4b159a7d65245c8de07f4537d3.zip
sched: replace INIT_COMPLETION with reinit_completion
For the casual device driver writer, it is hard to remember when to use init_completion (to init a completion structure) or INIT_COMPLETION (to *reinit* a completion structure). Furthermore, while all other completion functions exepct a pointer as a parameter, INIT_COMPLETION does not. To make it easier to remember which function to use and to make code more readable, introduce a new inline function with the proper name and consistent argument type. Update the kernel-doc for init_completion while we are here. Signed-off-by: Wolfram Sang <wsa@the-dreams.de> Acked-by: Linus Walleij <linus.walleij@linaro.org> (personally at LCE13) Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/md/dm-bufio.h')
0 files changed, 0 insertions, 0 deletions