All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@osdl.org>,
	Arjan van de Ven <arjanv@infradead.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@suse.de>,
	David Howells <dhowells@redhat.com>,
	Alexander Viro <viro@ftp.linux.org.uk>,
	Oleg Nesterov <oleg@tv-sign.ru>, Paul Jackson <pj@sgi.com>
Subject: Re: [patch 05/15] Generic Mutex Subsystem, mutex-core.patch
Date: Sun, 18 Dec 2005 22:56:00 -0500	[thread overview]
Message-ID: <1134964560.13138.220.camel@localhost.localdomain> (raw)
In-Reply-To: <20051219013718.GA28038@elte.hu>

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



  reply	other threads:[~2005-12-19  3:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19  1:37 [patch 05/15] Generic Mutex Subsystem, mutex-core.patch Ingo Molnar
2005-12-19  3:56 ` Steven Rostedt [this message]
2005-12-19  4:15 ` Steven Rostedt
2005-12-19  4:21 ` Steven Rostedt
2005-12-19  4:43 ` Steven Rostedt
2005-12-19  5:00 ` Steven Rostedt
2005-12-19  5:09   ` Steven Rostedt
2005-12-19 16:51   ` Ingo Molnar
2005-12-19  5:12 ` Steven Rostedt
2005-12-19 16:43   ` Ingo Molnar
2005-12-19  5:16 ` Steven Rostedt
2005-12-21 16:21 ` Oleg Nesterov
2005-12-21 15:57   ` Ingo Molnar
2005-12-21 17:51     ` Oleg Nesterov
2005-12-21 18:26       ` Ingo Molnar
2005-12-21 15:59   ` Ingo Molnar
2005-12-21 16:02   ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1134964560.13138.220.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@infradead.org \
    --cc=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@tv-sign.ru \
    --cc=pj@sgi.com \
    --cc=torvalds@osdl.org \
    --cc=viro@ftp.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.