From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>
Subject: What's in v2.6.24-lockdep
Date: Thu, 11 Oct 2007 23:03:03 +0200 [thread overview]
Message-ID: <1192136583.5797.20.camel@lappy> (raw)
Hi,
A heads up of what I inted to present for merging in v2.6.24.
- Peter (who is new at this game) Zijlstra
against the current x86 tree
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-lockdep.git v2.6.24-lockdep
Gregory Haskins (1):
lockdep: fix mismatched lockdep_depth/curr_chain_hash
Heiko Carstens (1):
lockdep: s390: connect the sysexit hook
Peter Zijlstra (8):
lockdep: maintainers
lockdep: fixup mutex annotations
lockdep: syscall exit check
lockdep: i386: connect the sysexit hook
lockdep: x86_64: connect the sysexit hook
lockdep: annotate journal_start()
lockdep: annotate rcu_read_{,un}lock{,_bh}
lockdep: annotate kprobes irq fiddling
Tim Pepper (1):
lockdep: Avoid /proc/lockdep & lock_stat infinite output
MAINTAINERS | 9 ++++++
arch/s390/kernel/entry.S | 12 ++++++++
arch/s390/kernel/entry64.S | 9 ++++++
arch/x86/kernel/entry_32.S | 4 +++
arch/x86/kernel/entry_64.S | 23 +++++++--------
arch/x86/kernel/kprobes_32.c | 7 +++++
arch/x86/kernel/kprobes_64.c | 7 +++++
arch/x86/lib/thunk_64.S | 4 +++
fs/jbd/transaction.c | 9 ++++++
include/asm-x86/irqflags_32.h | 13 +++++++++
include/asm-x86/irqflags_64.h | 14 +++++++++
include/linux/jbd.h | 5 +++
include/linux/lockdep.h | 9 ++++++
include/linux/mutex.h | 9 ++++--
include/linux/rcupdate.h | 14 +++++++++
kernel/lockdep.c | 26 ++++++++++++++---
kernel/lockdep_proc.c | 61 ++++++++++++++++++++++++++++-------------
kernel/mutex.c | 35 +++++++++++++----------
kernel/rcupdate.c | 8 +++++
19 files changed, 224 insertions(+), 54 deletions(-)
reply other threads:[~2007-10-11 21:04 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=1192136583.5797.20.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.