From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de (verein.lst.de [213.95.11.210]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 85DD7DDE1E for ; Mon, 5 May 2008 16:02:05 +1000 (EST) Date: Mon, 5 May 2008 08:01:54 +0200 From: Christoph Hellwig To: Paul Mackerras Subject: Re: WARNING: mutexes are preferred for single holder semaphores Message-ID: <20080505060154.GA12393@lst.de> References: <20080504204104.7eea7618@lappy.seanm.ca> <18462.27991.229693.188377@cargo.ozlabs.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <18462.27991.229693.188377@cargo.ozlabs.ibm.com> Cc: Sean MacLennan , linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, May 05, 2008 at 12:13:43PM +1000, Paul Mackerras wrote: > Sean MacLennan writes: > > > This is a bit OT, but I got the warning in the subject from > > checkpatch.pl for a piece of code. The code *is* using a mutex. Does it > > actually mean I shouldn't use a mutex? > > I don't require zero checkpatch warnings or errors on patches before I > accept them. If what checkpatch is saying is rubbish, just ignore it. Current versions don't spew much rubbish anymore, and this one certainly isn't.