The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Matthias Kaehlcke <matthias.kaehlcke@gmail.com>,
	chas@cmf.nrl.navy.mil, ecd@atecom.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use spinlock instead of binary mutex in idt77252 driver
Date: Mon, 23 Apr 2007 09:17:53 +0100	[thread overview]
Message-ID: <20070423081753.GA27664@infradead.org> (raw)
In-Reply-To: <45C4C5F0-4F09-416D-A237-82FC28DF1883@mac.com>

On Sun, Apr 22, 2007 at 07:50:36PM -0400, Kyle Moffett wrote:
> On Apr 22, 2007, at 17:39:59, Matthias Kaehlcke wrote:
> >use spinlock instead of binary mutex in idt77252 driver
> 
> I think you really meant: "Use mutex instead of binary semaphore in  
> idt77252 driver", since this is a binary semaphore (not a mutex,  
> which are always binary):

And the binary semaphore terminology i a little confusing. struct
semaphore is a full counting semaphore that is only used as a binary
semaphore if we want to speak in CS terms.  Than everyone else just
caled them semaphore before these patches started to show up :)


  parent reply	other threads:[~2007-04-23  8:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-22 21:39 [PATCH] use spinlock instead of binary mutex in idt77252 driver Matthias Kaehlcke
2007-04-22 23:50 ` Kyle Moffett
2007-04-23  6:55   ` Matthias Kaehlcke
2007-04-23  7:16     ` Eddie C. Dost
2007-04-23  7:40       ` Matthias Kaehlcke
2007-04-23  7:40         ` Eddie C. Dost
2007-04-23  7:57           ` Matthias Kaehlcke
2007-04-23  8:02           ` Satyam Sharma
2007-04-23  8:17   ` Christoph Hellwig [this message]
2007-04-23  8:35     ` Matthias Kaehlcke
2007-04-22 23:52 ` Satyam Sharma

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=20070423081753.GA27664@infradead.org \
    --to=hch@infradead.org \
    --cc=chas@cmf.nrl.navy.mil \
    --cc=ecd@atecom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.kaehlcke@gmail.com \
    --cc=mrmacman_g4@mac.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox