From: Tejun Heo <tj@kernel.org>
To: Namhyung Kim <namhyung@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] workqueue: mark lock acquisition on worker_maybe_bind_and_lock()
Date: Mon, 23 Aug 2010 11:41:18 +0200 [thread overview]
Message-ID: <4C72423E.3000402@kernel.org> (raw)
In-Reply-To: <1282486783-4573-2-git-send-email-namhyung@gmail.com>
On 08/22/2010 04:19 PM, Namhyung Kim wrote:
> worker_maybe_bind_and_lock() actually grabs gcwq->lock but was missing proper
> annotation. Add it. So this patch will remove following sparse warnings:
>
> kernel/workqueue.c:1214:13: warning: context imbalance in 'worker_maybe_bind_and_lock' - wrong count at exit
> arch/x86/include/asm/irqflags.h:44:9: warning: context imbalance in 'worker_rebind_fn' - unexpected unlock
> kernel/workqueue.c:1991:17: warning: context imbalance in 'rescuer_thread' - unexpected unlock
>
> Signed-off-by: Namhyung Kim <namhyung@gmail.com>
applied to wq#for-linus. Thanks.
Also, please considering putting related patches into a thread. For
short series, just chaining them is good enough (ie. patch n+1 is
reply to patch n). For longer series, writing up a head message with
overall description, diffstat and other general info about the patch
series and making all patches reaplies to the head message is a good
idea.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-08-23 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 14:19 [PATCH 2/2] workqueue: mark lock acquisition on worker_maybe_bind_and_lock() Namhyung Kim
2010-08-23 9:41 ` Tejun Heo [this message]
2010-08-23 15:01 ` Namhyung Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C72423E.3000402@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox