Re: [PATCH 13/13 v3] tracing: Comment the use of event_mutex withtrace event flags
From: Steven Rostedt
Date: Fri May 14 2010 - 20:44:53 EST
On Fri, 2010-05-14 at 18:21 -0400, Mathieu Desnoyers wrote:
> * Steven Rostedt (rostedt@xxxxxxxxxxx) 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@xxxxxxxxxxxx>
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/