From: Greg KH <greg@kroah.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/3] struct class sem to mutex converting
Date: Wed, 14 May 2008 08:57:29 -0700 [thread overview]
Message-ID: <20080514155729.GC28594@kroah.com> (raw)
In-Reply-To: <a8e1da0805131834g759523bfw396b0daa532252f9@mail.gmail.com>
On Wed, May 14, 2008 at 09:34:13AM +0800, Dave Young wrote:
> On Wed, May 14, 2008 at 6:01 AM, Greg KH <greg@kroah.com> wrote:
> > On Fri, May 09, 2008 at 03:22:31PM +0800, Dave Young wrote:
> > > The class_device is already removed, so do the class->sem to mutex converting.
> >
> > Are you sure this will work? Have you tried running lockdep to verify
> > that there are no problems here? People have tried this in the past
> > with devices and I don't think it will work here either :(
>
> Yes, lockdep doesn't generate warnings on my side.
I think Andrew's recent post to linux-scsi proves this is incorrect :)
> I ever wanted to do the conversion, please see:
> http://lkml.org/lkml/2008/1/12/49
>
> The result is that device sem2mutex is not possible now, but class
> sem2mutex is possible. After the class_device removing, all the
> class->sem usage exist in class.c except for i2c part.
>
> So I make i2c to use class_for_each_device api, so we can do the
> class->sem conversion.
Ah, I didn't realize that the i2c patch was required. Let me know when
Jean takes that patch in his tree.
thanks,
greg k-h
prev parent reply other threads:[~2008-05-14 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 7:22 [PATCH 2/3] struct class sem to mutex converting Dave Young
2008-05-13 22:01 ` Greg KH
2008-05-14 1:34 ` Dave Young
2008-05-14 15:57 ` Greg KH [this message]
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=20080514155729.GC28594@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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