From: Ingo Molnar <mingo@elte.hu>
To: Jason Baron <jbaron@redhat.com>
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: Re: [PATCH 0/3] add tracepoints docbook (take #2)
Date: Fri, 1 May 2009 16:55:28 +0200 [thread overview]
Message-ID: <20090501145528.GA7618@elte.hu> (raw)
In-Reply-To: <20090501142455.GA3111@redhat.com>
* Jason Baron <jbaron@redhat.com> wrote:
> On Thu, Apr 30, 2009 at 01:29:08PM -0400, Jason Baron wrote:
>
> > 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.
> >
>
> hi,
>
> i'd also like to get some agreement that future tracepoints need
> to have this sort of documentation included when they are
> submitted. Also, I'd like people who have already submitted
> tracepoints to go back and add this kind of documentation. I'll
> volunteer to police the effort if we agree it should be done.
sure - but sending patches would be even more useful than policing
:)
Ingo
prev parent reply other threads:[~2009-05-01 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 17:29 [PATCH 0/3] add tracepoints docbook (take #2) Jason Baron
2009-04-30 17:29 ` [PATCH 1/3] make kernel-doc understand TRACE_EVENT() macro " 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 [this message]
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=20090501145528.GA7618@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--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