From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758479AbZDOGfw (ORCPT ); Wed, 15 Apr 2009 02:35:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753704AbZDOGfl (ORCPT ); Wed, 15 Apr 2009 02:35:41 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:53761 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751424AbZDOGfk (ORCPT ); Wed, 15 Apr 2009 02:35:40 -0400 Date: Wed, 15 Apr 2009 08:34:05 +0200 From: Ingo Molnar To: Steven Rostedt Cc: linux-kernel@vger.kernel.org, Andrew Morton , Thomas Gleixner , Peter Zijlstra , Frederic Weisbecker , Theodore Tso , Arjan van de Ven , Christoph Hellwig , Mathieu Desnoyers , Jeremy Fitzhardinge , Lai Jiangshan , Zhaolei , Li Zefan , KOSAKI Motohiro , Masami Hiramatsu , "Frank Ch. Eigler" , Tom Zanussi , Jiaying Zhang , Michael Rubin , Martin Bligh Subject: Re: [PATCH 2/4] tracing/events: fix lockdep system name Message-ID: <20090415063405.GD12040@elte.hu> References: <20090415031511.128139334@goodmis.org> <20090415031604.933829085@goodmis.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090415031604.933829085@goodmis.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Steven Rostedt wrote: > From: Steven Rostedt > > 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