mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: John Lenz <jelenz@students.wisc.edu>
Cc: Andrew Zabolotny <zap@homelink.ru>, linux-kernel@vger.kernel.org
Subject: Re: Backlight and LCD module patches [2]
Date: Fri, 13 Aug 2004 16:27:40 -0700	[thread overview]
Message-ID: <20040813232739.GB5063@kroah.com> (raw)
In-Reply-To: <20040725215917.GA7279@hydra.mshome.net>

On Sun, Jul 25, 2004 at 04:59:17PM -0500, John Lenz wrote:
> The problem I see is that we would like something like a bus to match  
> together class devices.  What would be really nice is something like  
> this.
> 
> struct class_match {
>  struct class *class1;
>  struct class *class2;
> 
>  int (*match)(struct class_device *dev1, struct class_device *dev2);
> };
> 
> This class match structure would be very similar to a bus, in that it  
> matches together two classes instead of matching a device to a driver.   
> All the class code would have to do is call the match function for all  
> possible combinations of class devices in class1 and in class2.  If  
> match returned true, then it would create symbolic links between the  
> two.

Care to provide a proposed implementation of this functionality?

thanks,

greg k-h

  parent reply	other threads:[~2004-08-13 23:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 18:35 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 [this message]
2004-08-21  2:51     ` John Lenz
2004-09-05 15:00       ` Greg KH
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=20040813232739.GB5063@kroah.com \
    --to=greg@kroah.com \
    --cc=jelenz@students.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zap@homelink.ru \
    /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

all inboxes | Powered by JetHome®