[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1273884280.27703.3131.camel@gandalf.stny.rr.com>
Date: Fri, 14 May 2010 20:44:40 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Masami Hiramatsu <mhiramat@...hat.com>,
Tom Zanussi <tzanussi@...il.com>
Subject: Re: [PATCH 13/13 v3] tracing: Comment the use of event_mutex with
trace event flags
On Fri, 2010-05-14 at 18:21 -0400, Mathieu Desnoyers wrote:
> * Steven Rostedt (rostedt@...dmis.org) wrote:
> > + * Note: Reads of flags do not hold the event_mutex since
> > + * they occur in critical sections. But the way flags
> > + * is currently used, these changes do no affect the code
> > + * except that when a change is made, it may have a slight
> > + * delay in propagating the changes to other CPUs due to
> > + * cacheing and such.
>
> cacheing -> caching ?
hehe, I need spellcheck. I first wrote "caching", and thought to myself,
that looked wrong. Then I added the 'e'. Oh well.
>
> Besides this minor nit:
>
> Acked-by: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Thanks!
-- Steve
>
> > */
> > unsigned int flags;
> >
> > --
> > 1.7.0
> >
> >
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists