From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] workqueue changes for 3.5-rc1
Date: Tue, 22 May 2012 10:16:31 -0700 [thread overview]
Message-ID: <20120522171631.GE14339@google.com> (raw)
Hello, Linus.
Please pull from the following branch to receive workqueue changes for
3.5-rc1.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-3.5
Nothing exciting. Most are updates to debug stuff and related fixes.
Two not-too-critical bugs are fixed - WARN_ON() triggering spurious
during cpu offlining and unlikely lockdep related oops.
Thanks.
Dan Carpenter (1):
workqueue: change BUG_ON() to WARN_ON()
Peter Zijlstra (1):
lockdep: fix oops in processing workqueue
Stephen Boyd (2):
trace: Remove unused workqueue tracer
workqueue: Catch more locking problems with flush_work()
Tejun Heo (1):
workqueue: skip nr_running sanity check in worker_enter_idle() if trustee is active
include/linux/lockdep.h | 18 +++
kernel/timer.c | 4 +-
kernel/trace/Makefile | 1 -
kernel/trace/trace_workqueue.c | 300 ----------------------------------------
kernel/workqueue.c | 21 +++-
5 files changed, 38 insertions(+), 306 deletions(-)
delete mode 100644 kernel/trace/trace_workqueue.c
--
tejun
reply other threads:[~2012-05-22 17:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120522171631.GE14339@google.com \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome