From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/2] [GIT PULL] ftrace updates for 2.6.30
Date: Mon, 30 Mar 2009 14:41:49 -0400 [thread overview]
Message-ID: <20090330184149.866994402@goodmis.org> (raw)
Ingo,
Please pull the latest tip/tracing/ftrace tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/tracing/ftrace
Steven Rostedt (2):
function-graph: allow unregistering twice
ring-buffer: do not remove reader page from list on ring buffer free
----
kernel/trace/ftrace.c | 4 ++++
kernel/trace/ring_buffer.c | 1 -
2 files changed, 4 insertions(+), 1 deletions(-)
--
next reply other threads:[~2009-03-30 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 18:41 Steven Rostedt [this message]
2009-03-30 18:41 ` [PATCH 1/2] function-graph: allow unregistering twice Steven Rostedt
2009-03-30 18:41 ` [PATCH 2/2] ring-buffer: do not remove reader page from list on ring buffer free Steven Rostedt
2009-04-01 12:49 ` [PATCH 0/2] [GIT PULL] ftrace updates for 2.6.30 Ingo Molnar
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=20090330184149.866994402@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--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.