Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751330AbVLSD4x (ORCPT ); Sun, 18 Dec 2005 22:56:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751333AbVLSD4x (ORCPT ); Sun, 18 Dec 2005 22:56:53 -0500 Received: from ms-smtp-01.nyroc.rr.com ([24.24.2.55]:7094 "EHLO ms-smtp-01.nyroc.rr.com") by vger.kernel.org with ESMTP id S1751330AbVLSD4w (ORCPT ); Sun, 18 Dec 2005 22:56:52 -0500 Subject: Re: [patch 05/15] Generic Mutex Subsystem, mutex-core.patch From: Steven Rostedt To: Ingo Molnar Cc: linux-kernel@vger.kernel.org, Linus Torvalds , Andrew Morton , Arjan van de Ven , Alan Cox , Christoph Hellwig , Andi Kleen , David Howells , Alexander Viro , Oleg Nesterov , Paul Jackson In-Reply-To: <20051219013718.GA28038@elte.hu> References: <20051219013718.GA28038@elte.hu> Content-Type: text/plain Date: Sun, 18 Dec 2005 22:56:00 -0500 Message-Id: <1134964560.13138.220.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 634 Lines: 17 On Mon, 2005-12-19 at 02:37 +0100, Ingo Molnar wrote: > + * These semantics are fully enforced when DEBUG_MUTEXESS is > + * enabled. Furthermore, besides enforcing the above rules, the mutex > + * debugging code also implements a number of additional features > + * that make lock debugging easier and faster: Silly question: Is MUTEXESS a proper name, and what does it mean? -- Steve - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/