No functional change. The comment of function manage_workers() RETURNS description is obvious wrong, same as the CONTEXT. Fix it.
Signed-off-by: Libin <[email protected]> --- kernel/workqueue.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/kernel/workqueue.c b/kernel/workqueue.c index 26644ce..46a0de0 100644 --- a/kernel/workqueue.c +++ b/kernel/workqueue.c @@ -2034,8 +2034,11 @@ static bool maybe_destroy_workers(struct worker_pool *pool) * multiple times. Does GFP_KERNEL allocations. * * RETURNS: - * spin_lock_irq(pool->lock) which may be released and regrabbed - * multiple times. Does GFP_KERNEL allocations. + * %false if the pool don't need management and the caller can safely + * start processing works, %true indicates that the function released + * pool->lock and reacquired it to perform some management function + * and that the conditions that the caller verified while holding the + * lock before calling the function might no longer be true. */ static bool manage_workers(struct worker *worker) { -- 1.8.2.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
