public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	rostedt@goodmis.org, fweisbec@gmail.com,
	mathieu.desnoyers@polymtl.ca, randy.dunlap@oracle.com,
	wcohen@redhat.com
Subject: [PATCH 0/3] add tracepoints docbook (take #2)
Date: Thu, 30 Apr 2009 13:29:08 -0400	[thread overview]
Message-ID: <cover.1241107197.git.jbaron@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

Jason Baron (3):
  -make kernel-doc understand TRACE_EVENT() macro
  -add new tracepoints docbook
  -add irq tracepoint documentation

 Documentation/DocBook/Makefile        |    3 +-
 Documentation/DocBook/tracepoint.tmpl |   89 +++++++++++++++++++++++++++++++++
 include/trace/events/irq.h            |   46 +++++++++++++++--
 scripts/kernel-doc                    |   22 ++++++++
 4 files changed, 155 insertions(+), 5 deletions(-)
 create mode 100644 Documentation/DocBook/tracepoint.tmpl


             reply	other threads:[~2009-04-30 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 17:29 Jason Baron [this message]
2009-04-30 17:29 ` [PATCH 1/3] make kernel-doc understand TRACE_EVENT() macro (take #2) Jason Baron
2009-05-01 13:28   ` [tip:tracing/core] kerneldoc, tracing: " tip-bot for Jason Baron
2009-04-30 17:29 ` [PATCH 2/3] add new tracepoints docbook " Jason Baron
2009-05-01 13:28   ` [tip:tracing/core] tracing: add new tracepoints docbook tip-bot for Jason Baron
2009-04-30 17:29 ` [PATCH 3/3] add irq tracepoint documentation (take #2) Jason Baron
2009-05-01 13:28   ` [tip:tracing/core] tracing: add irq tracepoint documentation tip-bot for Jason Baron
2009-05-01 14:24 ` [PATCH 0/3] add tracepoints docbook (take #2) Jason Baron
2009-05-01 14:55   ` Ingo Molnar

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=cover.1241107197.git.jbaron@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