From: Jason Baron <jbaron@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, mingo@elte.hu, rostedt@goodmis.org,
fweisbec@gmail.com, mathieu.desnoyers@polymtl.ca,
randy.dunlap@oracle.com, wcohen@redhat.com
Subject: [PATCH 0/3] add tracepoint docbook
Date: Wed, 29 Apr 2009 13:45:19 -0400 [thread overview]
Message-ID: <200904291745.n3THjJSe019520@ns3.rdu.redhat.com> (raw)
The following patches add a new tracepoint docbook. Since tracepoints can
be defined by various macros and in various files, I think it important
to clearly document the available tracepoints, as Andrew has pointed out.
This helps us see what we have and what we don't have. If this patch is
accepted, I hope that others will add docbook style comments, so we can
have a complete accounting of the kernel's tracepoints.
The docbook from these patch series can be viewed at:
http://people.redhat.com/~jbaron/tracepoints/
thanks,
-Jason
next reply other threads:[~2009-04-29 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 17:45 Jason Baron [this message]
2009-04-29 18:17 ` Mathieu Desnoyers
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=200904291745.n3THjJSe019520@ns3.rdu.redhat.com \
--to=jbaron@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=rostedt@goodmis.org \
--cc=wcohen@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
all inboxes | Powered by JetHome®