[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090415063405.GD12040@elte.hu>
Date: Wed, 15 Apr 2009 08:34:05 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Theodore Tso <tytso@....edu>,
Arjan van de Ven <arjan@...radead.org>,
Christoph Hellwig <hch@....de>,
Mathieu Desnoyers <compudj@...stal.dyndns.org>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Lai Jiangshan <laijs@...fujitsu.com>,
Zhaolei <zhaolei@...fujitsu.com>, Li Zefan <lizf@...fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Masami Hiramatsu <mhiramat@...hat.com>,
"Frank Ch. Eigler" <fche@...stic.org>,
Tom Zanussi <tzanussi@...il.com>,
Jiaying Zhang <jiayingz@...gle.com>,
Michael Rubin <mrubin@...gle.com>,
Martin Bligh <mbligh@...gle.com>
Subject: Re: [PATCH 2/4] tracing/events: fix lockdep system name
* Steven Rostedt <rostedt@...dmis.org> wrote:
> From: Steven Rostedt <srostedt@...hat.com>
>
> Impact: fix compile error of lockdep event tracer
>
> Ingo Molnar pointed out that the system name for the lockdep
> tracer was "lock" which is used to include the event trace file
> name. It should be "lockdep"
btw, i think it would be better to name it 'lock', all around -
i.e. lock.h, lock subsystem, etc.
lockdep is the 'lock dependency tracking engine'.
The locking related tracepoints here are implemented via lockdep
right now, but that might be done differently in the future - and
we dont want to do a rename (or live with a misnomer) then.
Ingo
--
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