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/6] [GIT PULL] tracing: various fixes
Date: Mon, 14 Sep 2009 12:33:55 -0400 [thread overview]
Message-ID: <20090914163355.162375454@goodmis.org> (raw)
Ingo,
Please pull the latest tip/tracing/core tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/tracing/core
Li Zefan (3):
tracing: fix F_printk() typos
ftrace: add compile-time check on F_printk()
tracing: remove some unused macros
Steven Rostedt (3):
tracing: add static to generated TRACE_EVENT functions
tracing: have TRACE_EVENT macro use __flags to not shadow parameter
tracing: make testing syscall events a separate configuration
----
include/trace/ftrace.h | 8 ++--
kernel/trace/Kconfig | 12 +++++++
kernel/trace/trace_entries.h | 27 +++++----------
kernel/trace/trace_events.c | 14 ++++++++-
kernel/trace/trace_export.c | 71 ++++++++++++++++++++++++-----------------
5 files changed, 79 insertions(+), 53 deletions(-)
--
next reply other threads:[~2009-09-14 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 16:33 Steven Rostedt [this message]
2009-09-14 16:33 ` [PATCH 1/6] tracing: add static to generated TRACE_EVENT functions Steven Rostedt
2009-09-14 16:33 ` [PATCH 2/6] tracing: have TRACE_EVENT macro use __flags to not shadow parameter Steven Rostedt
2009-09-14 16:33 ` [PATCH 3/6] tracing: fix F_printk() typos Steven Rostedt
2009-09-14 16:33 ` [PATCH 4/6] ftrace: add compile-time check on F_printk() Steven Rostedt
2009-09-14 16:34 ` [PATCH 5/6] tracing: remove some unused macros Steven Rostedt
2009-09-14 16:34 ` [PATCH 6/6] tracing: make testing syscall events a separate configuration Steven Rostedt
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=20090914163355.162375454@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®