From: Greg KH <greg@kroah.com>
To: John Lenz <lenz@cs.wisc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Backlight and LCD module patches [2]
Date: Sun, 5 Sep 2004 11:00:32 -0400 [thread overview]
Message-ID: <20040905150032.GF12701@kroah.com> (raw)
In-Reply-To: <1093056693l.30570l.0l@hydra>
On Sat, Aug 21, 2004 at 02:51:33AM +0000, John Lenz wrote:
>
> Here. A few notes on the implementation. I have a global lock protecting
> all match operations because otherwise we get a dining philosophers problem.
> (Say the same class is in two class_match structures, class1 in the first
> one and class2 in the second...)
You also have some duplicated code in one function, which implies that
you didn't test this patch (it's in the updated patch you sent me too) :)
> The bigger question of how should we be linking these together in the first
> place?
I thought you only wanted the ability to actually find the different
class devices. Then the code would take it from there. Not this
complex driver core linking logic that you implemented.
> Instead of using this class_match stuff, we could use class_interface.
Exactly. Why don't you all use that instead?
thanks,
greg k-h
next prev parent reply other threads:[~2004-09-06 2:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 18:35 Backlight and LCD module patches [2] Andrew Zabolotny
2004-06-25 15:33 ` Pavel Machek
2004-07-25 21:59 ` John Lenz
2004-07-28 18:11 ` Andrew Zabolotny
2004-07-29 23:25 ` John Lenz
2004-07-30 0:06 ` Andrew Zabolotny
2004-07-30 0:49 ` John Lenz
2004-07-30 20:02 ` Andrew Zabolotny
2004-07-31 22:17 ` John Lenz
2004-08-01 17:37 ` Andrew Zabolotny
2004-08-13 23:27 ` Greg KH
2004-08-21 2:51 ` John Lenz
2004-09-05 15:00 ` Greg KH [this message]
2004-09-06 7:32 ` John Lenz
2004-08-22 23:07 ` John Lenz
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=20040905150032.GF12701@kroah.com \
--to=greg@kroah.com \
--cc=lenz@cs.wisc.edu \
--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