Subject: Re: [patch 00/62] sem2mutex: -V1
From: Arjan van de Ven <arjan@infradead.org>
To: chaosite@gmail.com
Cc: Ingo Molnar <mingo@elte.hu>, Ingo Oeser <ioe-lkml@rameria.de>,
       linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
       Linus Torvalds <torvalds@osdl.org>,
       Jes Sorensen <jes@trained-monkey.org>, Greg KH <greg@kroah.com>
In-Reply-To: <43C815E3.10005@gmail.com>
References: <20060113124402.GA7351@elte.hu>
	 <200601131400.00279.baldrick@free.fr> <20060113134412.GA20339@elte.hu>
	 <200601131925.34971.ioe-lkml@rameria.de> <20060113195658.GA3780@elte.hu>
	 <43C815E3.10005@gmail.com>
Content-Type: text/plain
Date: Fri, 13 Jan 2006 22:25:54 +0100
Message-Id: <1137187555.2975.13.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 974
Lines: 31

On Fri, 2006-01-13 at 23:04 +0200, Matan Peled wrote:
> Ingo Molnar wrote:
> > Ingo Oeser wrote:
> >> Could we get for each of these and a mutex:
> >>
> >>  - description 
> >>  - common use case
> >>  - small argument why this and nothing else should be used there
> > 
> > like ... Documentation/mutex-design.txt?
> 
> I think what he wanted was an explanation for the change of each and every 
> sem... Which is kind of hard with automated tools.
`
it's also HIGHLY repetitive.
1) The process is : Look at semaphore and it's uses.
2) Decide it's a mutex
3) Run script to convert to mutex
4) Run script to validate the conversion
5) build+boot test

I can't think of a way to describe that uniquely different for each
one ;0


-
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/