lkml.org 
[lkml]   [2009]   [Dec]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [tip:perf/core] tracing: Add DEFINE_EVENT(), DEFINE_SINGLE_EVENT() support to docbook

* Steven Rostedt <rostedt@goodmis.org> wrote:

> 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@redhat.com>
> > AuthorDate: Tue, 1 Dec 2009 12:18:49 -0500
> > Committer: Ingo Molnar <mingo@elte.hu>
> > 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()

Hm, that's a bit too long. How about 'DEFINE_CLASS_EVENT()' as a
compromise? It's similarly short-ish to TRACE_EVENT(), and it also
conveys the fact that we create both a class and an event there.

The full series would thus be:

DECLARE_EVENT_CLASS
DEFINE_EVENT
DEFINE_CLASS_EVENT

hm?

Ingo


\
 
 \ /
  Last update: 2009-12-02 15:05    [W:0.054 / U:0.432 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site