diff options
author | Wolfram Sang <wsa@the-dreams.de> | 2013-11-14 22:32:01 (GMT) |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2013-11-15 00:32:21 (GMT) |
commit | c32f74ab2872994bc8336ed367313da3139350ca (patch) | |
tree | 447daece4f5eac46f8af3a5df7d407dcbc011c34 /drivers/net/wireless/Makefile | |
parent | 406bf31893163cbe5b0b03a281685c7dc95c9380 (diff) | |
download | linux-c32f74ab2872994bc8336ed367313da3139350ca.tar.xz |
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)
Cc: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/net/wireless/Makefile')
0 files changed, 0 insertions, 0 deletions