On Wed, 2009-12-02 at 10:42 +0000, tip-bot for Jason Baron wrote: > Commit-ID: 3a9089fd78367e2c6c815129030b790a0f5c2715 > Gitweb: http://git.kernel.org/tip/3a9089fd78367e2c6c815129030b790a0f5c2715 > Author: Jason Baron <jbaron@xxxxxxxxxx> > AuthorDate: Tue, 1 Dec 2009 12:18:49 -0500 > Committer: Ingo Molnar <mingo@xxxxxxx> > CommitDate: Wed, 2 Dec 2009 09:57:37 +0100 > > tracing: Add DEFINE_EVENT(), DEFINE_SINGLE_EVENT() support to docbook Ug, I need more sleep, because I never noticed the "SINGLE" when I acked this :-p I thought the DEFINE_SINGLE_EVENT was still under discussion because it is a confusing name. I suggested to call it exactly what is was. DECLARE_CLASS_AND_DEFINE_EVENT() -- Steve > > The introduction of the new 'DECLARE_EVENT_CLASS()' obviates the > need for the 'TRACE_EVENT()' macro in some cases. Thus, docbook > style comments that used to live with 'TRACE_EVENT()' are now > moved to 'DEFINE_EVENT()'. Thus, we need to make the docbook > system understand the new 'DEFINE_EVENT()' macro. In addition > I've tried to futureproof the patch, by also adding support for > 'DEFINE_SINGLE_EVENT()', since there has been discussion about > renaming: TRACE_EVENT() -> DEFINE_SINGLE_EVENT(). > > Without this patch the tracepoint docbook fails to build. > > I've verified that this patch correctly builds the tracepoint > docbook which currently covers signals, and irqs. > > Changes in v2: > - properly indent perl 'if' statements > > Signed-off-by: Jason Baron <jbaron@xxxxxxxxxx> > Acked-by: Steven Rostedt <rostedt@xxxxxxxxxxx> > Acked-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx> > Cc: William Cohen <wcohen@xxxxxxxxxx> > Cc: Frederic Weisbecker <fweisbec@xxxxxxxxx> > Cc: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx> > Cc: Masami Hiramatsu <mhiramat@xxxxxxxxxx> > LKML-Reference: <200912011718.nB1HIn7t011371@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> > Signed-off-by: Ingo Molnar <mingo@xxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|