From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: [GIT PULL] lockdep updates
Date: Mon, 25 Feb 2008 23:17:08 +0100 [thread overview]
Message-ID: <1203977828.6242.220.camel@lappy> (raw)
Linus, please pull a few lockdep patches from:
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-lockdep.git v2.6.25-rc3-lockdep
---
Dale Farnsworth (1):
Subject: lockdep: include all lock classes in all_lock_classes
Peter Zijlstra (1):
lockdep: increase MAX_LOCK_DEPTH
include/linux/sched.h | 2 +-
kernel/lockdep.c | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
next reply other threads:[~2008-02-25 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 22:17 Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-30 17:34 [GIT PULL] lockdep updates Frederic Weisbecker
2010-05-03 7:23 ` Ingo Molnar
2010-05-03 13:00 ` Ingo Molnar
2010-05-03 13:47 ` Frederic Weisbecker
2008-01-16 9:28 Peter Zijlstra
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=1203977828.6242.220.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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