Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation

On Tue, Dec 13, 2005 at 10:48:19AM +0000, David Howells wrote:
> > > +#define is_mutex_locked(mutex)	((mutex)->state)
> > 
> > Let's keep the namespace consistent.  mutex_is_locked().
> 
> But that's a poor name: it turns it from a question into a statement:-(

Ah, but look at it in context of how it's used:

	if (is_mutex_locked())
That's gramatically incorrect!

	if (mutex_is_locked())
much better.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation
    • From: Andrew Morton <[email protected]>
  • [PATCH 1/19] MUTEX: Introduce simple mutex implementation
    • From: David Howells <[email protected]>
  • Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation
    • From: David Howells <[email protected]>

• Prev by Date: Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation
• Next by Date: Re: [patch 00/21] hrtimer - High-resolution timer subsystem
• Previous by thread: Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation
• Next by thread: Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]