From: Tom Zanussi <tzanussi@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, fweisbec@gmail.com, rostedt@goodmis.org,
lizf@cn.fujitsu.com
Subject: [PATCH 0/3] a few tracing bugfixes
Date: Tue, 6 Oct 2009 01:00:46 -0500 [thread overview]
Message-ID: <1254808849-7829-1-git-send-email-tzanussi@gmail.com> (raw)
Some fixes for a few things I noticed recently.
Tom Zanussi (3):
perf trace: Remove unused code in builtin-trace.c
perf trace: Update eval_flag() flags array to match interrupt.h
tracing/syscalls: Use long for syscall ret format and field
definitions
kernel/trace/trace_syscalls.c | 4 ++--
tools/perf/builtin-trace.c | 6 ------
tools/perf/util/trace-event-parse.c | 9 +++++----
3 files changed, 7 insertions(+), 12 deletions(-)
next reply other threads:[~2009-10-06 6:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 6:00 Tom Zanussi [this message]
2009-10-06 6:00 ` [PATCH 1/3] perf trace: Remove unused code in builtin-trace.c Tom Zanussi
2009-10-06 12:16 ` [tip:perf/urgent] " tip-bot for Tom Zanussi
2009-10-06 6:00 ` [PATCH 2/3] perf trace: Update eval_flag() flags array to match interrupt.h Tom Zanussi
2009-10-06 12:16 ` [tip:perf/urgent] " tip-bot for Tom Zanussi
2009-10-06 13:27 ` [PATCH 2/3] " Christoph Hellwig
2009-10-06 15:19 ` Frederic Weisbecker
2009-10-06 15:21 ` Christoph Hellwig
2009-10-06 15:22 ` Frederic Weisbecker
2009-10-06 15:24 ` Christoph Hellwig
2009-10-06 21:42 ` Frederic Weisbecker
2009-10-07 1:17 ` Steven Rostedt
2009-10-06 15:25 ` Frederic Weisbecker
2009-10-11 8:53 ` Ingo Molnar
2009-10-11 12:21 ` Christoph Hellwig
2009-10-16 8:47 ` Ingo Molnar
2009-10-06 6:00 ` [PATCH 3/3] tracing/syscalls: Use long for syscall ret format and field definitions Tom Zanussi
2009-10-06 7:15 ` Frédéric Weisbecker
2009-10-07 3:59 ` Tom Zanussi
2009-10-06 12:17 ` [tip:perf/urgent] " tip-bot for Tom Zanussi
2009-10-06 7:16 ` [PATCH 0/3] a few tracing bugfixes Frédéric Weisbecker
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=1254808849-7829-1-git-send-email-tzanussi@gmail.com \
--to=tzanussi@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®