From: Ingo Molnar <mingo@elte.hu>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Jason Baron <jbaron@redhat.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
rostedt@goodmis.org, fweisbec@gmail.com,
mathieu.desnoyers@polymtl.ca, wcohen@redhat.com
Subject: Re: [PATCH 1/3] make kernel-doc understand TRACE_EVENT() macro
Date: Wed, 29 Apr 2009 22:34:39 +0200 [thread overview]
Message-ID: <20090429203439.GD21421@elte.hu> (raw)
In-Reply-To: <49F8A7D1.6010307@oracle.com>
* Randy Dunlap <randy.dunlap@oracle.com> wrote:
> Jason Baron wrote:
> > Add support to kernel-doc for tracepoint comments above TRACE_EVENT()
> > macro definitions. Paves the way for tracepoint docbook.
> >
> >
> > Signed-off-by: Jason Baron <jbaron@redhat.com>
> >
> > ---
> > scripts/kernel-doc | 21 +++++++++++++++++++++
> > 1 files changed, 21 insertions(+), 0 deletions(-)
> >
> > diff --git a/scripts/kernel-doc b/scripts/kernel-doc
> > index 0f11870..9d9ab4b 100755
> > --- a/scripts/kernel-doc
> > +++ b/scripts/kernel-doc
> > @@ -1827,6 +1827,24 @@ sub reset_state {
> > $state = 0;
> > }
> >
> > +sub tracepoint_munge() {
> > + my $tracepointname = 0;
> > + my $tracepointargs = 0;
> > +
> > + if($prototype =~ m/TRACE_EVENT\((.*?),/) {
> > + $tracepointname = $1;
> > + }
> > + if($prototype =~ m/TP_PROTO\((.*?)\)/) {
> > + $tracepointargs = $1;
> > + }
> > + if (($tracepointname eq 0) || ($tracepointargs eq 0)) {
> > + print STDERR "Warning: Unrecognized tracepoint format: \n" .
> > + "$prototype\n"
>
> I'd prefer for this warning to use the usual kernel-doc warning format, with
> file:line information:
>
> print STDERR "Warning(${file}:$.): Unrecognized ....
Good point - i'll wait for v2. Or would you like to carry them in
your kernel-doc tree?
This bit:
include/trace/events/irq.h | 46 ++++++++++++++++++++++++++++++---
Has changed in the tracing tree so it's probably better to carry it
there - once your review feedback has been addressed and once your
Acked-by is propagated into the patches.
Thanks,
Ingo
next prev parent reply other threads:[~2009-04-29 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 17:45 Jason Baron
2009-04-29 19:17 ` Randy Dunlap
2009-04-29 20:34 ` Ingo Molnar [this message]
2009-04-29 22:03 ` Randy Dunlap
2009-04-30 14:48 ` 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=20090429203439.GD21421@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
all inboxes | Powered by JetHome®