[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080103074132.GA2000@ff.dom.local>
Date: Thu, 3 Jan 2008 08:41:32 +0100
From: Jarek Poplawski <jarkao2@...il.com>
To: Dave Young <hidave.darkstar@...il.com>
Cc: gregkh@...e.de, stern@...land.harvard.edu, peterz@...radead.org,
david-b@...bell.net, davem@...emloft.net, krh@...hat.com,
stefanr@...6.in-berlin.de, dbrownell@...rs.sourceforge.net,
James.Bottomley@...senpartnership.com, a.zummo@...ertech.it,
cbou@...l.ru, dwmw2@...radead.org, khali@...ux-fr.org,
i2c@...sensors.org, linux1394-devel@...ts.sourceforge.net,
spi-devel-general@...ts.sourceforge.net,
linux-scsi@...r.kernel.org, rtc-linux@...glegroups.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] convert semaphore to mutex in struct class
On Thu, Jan 03, 2008 at 03:21:36PM +0800, Dave Young wrote:
...
> I don't know if there's other possible warning places with this mutex
> or not, if you have any ideas about this, please tell me.
I think lockdep is just to tell such things. So, the question is, how
much it was tested already, because if there are many warnings
reported e.g. after merging to -mm, then this could be better to re-do
it this other way... But, I hope this will not be necessary.
Jarek P.
--
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