[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47588610.5010804@gmail.com>
Date: Thu, 06 Dec 2007 19:30:24 -0400
From: Kevin Winchester <kjwinchester@...il.com>
To: Daniel Walker <dwalker@...sta.com>
CC: Ingo Molnar <mingo@...e.hu>, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, linux@...mer.net,
jonathan@...masters.org, matthias.kaehlcke@...il.com
Subject: Re: [PATCH 3/3] printer port driver: semaphore to mutex
Daniel Walker wrote:
> On Thu, 2007-12-06 at 11:23 +0100, Ingo Molnar wrote:
>> * Daniel Walker <dwalker@...sta.com> wrote:
>>
>>> The port_mutex is actually a semaphore, so easily converted to a
>>> struct mutex.
>>>
>>> Signed-off-by: Daniel Walker <dwalker@...sta.com>
>> Acked-by: Ingo Molnar <mingo@...e.hu>
>>
>> cool. How far away are we from being able to remove all the semaphore
>> code? :-)
>
> I wish my 7 patches made a dent, but it's hasn't done much. ;(
>
> I would guess at least a week just to mop up the relatively easy ones..
> I've got 12 in my queue, and there still ~50 hopefully trivial ones
> still to be looked at.. Then another ~30 more difficult ones (that use
> init_MUTEX_LOCKED, or sema_init with 0 instead of 1) ..
>
I didn't realise there were so many of these patch sets still to go. I
could probably help out with some of them. Is there somewhere we could
keep track of which ones are left to do, and who is handling them? If
it would be helpful, I could go through all of the semaphore uses in the
tree and try to figure out which (if any) are true counting semaphores
that cannot be converted, and then I could post/send the list of
convertible cases. Would that be helpful, or has it already been done
somewhere else?
--
Kevin Winchester
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists