From: Masami Hiramatsu <mhiramat@redhat.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>,
Roland McGrath <roland@redhat.com>,
Jason Baron <jbaron@redhat.com>
Subject: Re: [PATCH -tip v3 1/3] tracepoint: Move signal sending tracepoint to events/signal.h
Date: Tue, 24 Nov 2009 21:00:00 -0000 [thread overview]
Message-ID: <4B0C495F.8000002@redhat.com> (raw)
In-Reply-To: <20091124204943.GA11300@redhat.com>
Oleg Nesterov wrote:
> On 11/20, Masami Hiramatsu wrote:
>>
>> +TRACE_EVENT(signal_generate,
>> +
>> + TP_PROTO(int sig, struct siginfo *info, struct task_struct *task),
>> +
>> + TP_ARGS(sig, info, p),
> ^^^
> s/p/task/ ?
Oops, right.
Thank you for reviewing!
>
> Oleg.
>
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-11-24 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 21:29 [PATCH -tip v3 0/3] tracepoint: Add signal events Masami Hiramatsu
2009-11-20 21:29 ` [PATCH -tip v3 1/3] tracepoint: Move signal sending tracepoint to events/signal.h Masami Hiramatsu
2009-11-24 20:55 ` Oleg Nesterov
2009-11-24 21:00 ` Masami Hiramatsu [this message]
2009-11-20 21:29 ` [PATCH -tip v3 2/3] tracepoint: Add signal deliver event Masami Hiramatsu
2009-11-20 21:30 ` [PATCH -tip v3 3/3] tracepoint: Add signal loss events Masami Hiramatsu
2009-11-23 17:59 ` [PATCH -tip v3 0/3] tracepoint: Add signal events Ingo Molnar
2009-11-24 21:28 ` Oleg Nesterov
2009-11-24 21:45 ` Masami Hiramatsu
2009-11-24 21:56 ` Ingo Molnar
2009-11-25 17:46 ` Oleg Nesterov
2009-11-23 23:01 ` Jason Baron
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=4B0C495F.8000002@redhat.com \
--to=mhiramat@redhat.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--cc=systemtap@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).