From: Daniel Walker <dwalker@fifo99.com>
To: jolsa@redhat.com
Cc: mingo@elte.hu, rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] tracing - signal tracer, support multiple pids in set_pid_ftrace
Date: Mon, 14 Sep 2009 06:59:55 -0700 [thread overview]
Message-ID: <1252936795.28368.217.camel@desktop> (raw)
In-Reply-To: <1252923251-6735-1-git-send-email-jolsa@redhat.com>
On Mon, 2009-09-14 at 12:14 +0200, jolsa@redhat.com wrote:
> 1/2 - signal trace
> 2/2 - multiple pids support for set_pid_ftrace file
The whole series several checkpatch errors. Could you fix those before
you take the RFC off this?
Daniel
next prev parent reply other threads:[~2009-09-14 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 10:14 [RFC PATCH 0/2] tracing - signal tracer, support multiple pids in set_pid_ftrace jolsa
2009-09-14 10:14 ` [RFC PATCH 1/2] tracing - signal tracer jolsa
2009-09-14 10:14 ` [RFC PATCH 2/2] tracing - support multiple pids in set_pid_ftrace file jolsa
2009-09-14 12:20 ` [RFC PATCH 0/2] tracing - signal tracer, support multiple pids in set_pid_ftrace Steven Rostedt
2009-09-14 13:59 ` Daniel Walker [this message]
2009-09-14 14:05 ` Jiri Olsa
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=1252936795.28368.217.camel@desktop \
--to=dwalker@fifo99.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.