public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
	        Roland McGrath <roland@redhat.com>,
	Oleg Nesterov <oleg@redhat.com>,
	        systemtap <systemtap@sources.redhat.com>,
	        DLE <dle-develop@lists.sourceforge.net>
Subject: Re: [PATCH -tip v2 0/3] tracepoint: Add signal events
Date: Thu, 19 Nov 2009 19:39:00 -0000	[thread overview]
Message-ID: <20091119193814.GB2625@redhat.com> (raw)
In-Reply-To: <20091118211609.20207.55487.stgit@dhcp-100-2-132.bos.redhat.com>

On Wed, Nov 18, 2009 at 04:16:09PM -0500, Masami Hiramatsu wrote:
> Hi,
> 
> These patches add signal related tracepoints including
> signal generation, delivery, and loss. First patch also
> moves signal-sending tracepoint from events/sched.h to
> events/signal.h.
> 
> Changes in v2
> - Add siginfo arguments
> 

hi Masami,

It would be really great if you could add docbook style comments to
your tracepoints. Here's the initial path I posted for the irq chapter:
http://lkml.indiana.edu/hypermail/linux/kernel/0904.3/02651.html

So you could add a new chapter for signals.

The current tracepoint docbook can be viewed at:

http://www.kernel.org/doc/htmldocs/tracepoint/

thanks,

-Jason

  parent reply	other threads:[~2009-11-19 19:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 21:14 Masami Hiramatsu
2009-11-18 21:14 ` [PATCH -tip v2 1/3] tracepoint: Move signal sending tracepoint to events/signal.h Masami Hiramatsu
2009-11-18 21:15 ` [PATCH -tip v2 2/3] tracepoint: Add signal deliver event Masami Hiramatsu
2009-11-18 21:15 ` [PATCH -tip v2 3/3] tracepoint: Add signal loss events Masami Hiramatsu
2009-11-19 19:39 ` Jason Baron [this message]
2009-11-20  0:37   ` [PATCH -tip v2 0/3] tracepoint: Add signal events Masami Hiramatsu

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=20091119193814.GB2625@redhat.com \
    --to=jbaron@redhat.com \
    --cc=dle-develop@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@redhat.com \
    --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).