From: Matthew Wilcox <matthew@wil.cx>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-scsi@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: lockdep whine in 2.6.26-rc2-mm1
Date: Mon, 19 May 2008 19:51:43 -0600 [thread overview]
Message-ID: <20080520015142.GJ2638@parisc-linux.org> (raw)
In-Reply-To: <a8e1da0805191827s6222ec65k8521359b188e6345@mail.gmail.com>
On Tue, May 20, 2008 at 09:27:59AM +0800, Dave Young wrote:
> > The question isn't whether there is or isn't this kind of use right now.
> > The question is whether there might be this kind of use in the future,
> > and if there is, whether we'd like lockdep to warn us.
>
> In the future, IMHO, the class_interface should go away just as
> class_device. If that happened this problem would going away as well.
Go away ... and be replaced by something else, right? I mean, it's not
like we don't have a need to bind two kinds of driver to the same
device. So we're going to continue to have the situation where you can
register a new kind of driver and want to create new devices, so we'll
still have a nesting of some kind.
> Your idea is good. But as I said above, for current situation there's
> no potential problems except class_interface usage, and the
> class_interface will go away
> in the future.
>
> So IMO It's not necessary to do this for all classes.
Assuming your analysis is correct, of course.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-05-20 1:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 7:09 lockdep whine in 2.6.26-rc2-mm1 Andrew Morton
2008-05-14 15:56 ` Greg KH
2008-05-14 16:24 ` Matthew Wilcox
2008-05-15 5:47 ` Dave Young
2008-05-15 9:01 ` Dave Young
2008-05-15 11:52 ` Matthew Wilcox
2008-05-17 10:14 ` Dave Young
2008-05-19 5:20 ` Dave Young
2008-05-19 7:56 ` Dave Young
2008-05-19 10:23 ` Matthew Wilcox
2008-05-20 1:27 ` Dave Young
2008-05-20 1:51 ` Matthew Wilcox [this message]
2008-05-20 18:07 ` Greg KH
2008-05-21 3:20 ` Dave Young
2008-05-21 4:38 ` Greg KH
2008-05-15 5:50 ` Dave Young
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=20080520015142.GJ2638@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=hidave.darkstar@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-scsi@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