All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Adam Belay <abelay@novell.com>
Cc: rml@novell.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] add driver matching priorities
Date: Thu, 10 Feb 2005 10:33:38 -0800	[thread overview]
Message-ID: <20050210183338.GA9308@kroah.com> (raw)
In-Reply-To: <1108055918.3423.23.camel@localhost.localdomain>

On Thu, Feb 10, 2005 at 12:18:37PM -0500, Adam Belay wrote:
> 
> The second "*match" function in "struct device_driver" gives the driver
> a chance to evaluate it's ability of controlling the device and solves a
> few problems with the current implementation.  (ex. it's not possible to
> detect ISA Modems with only a list of PnP IDs, and some PCI devices
> support a pool of IDs that is too large to put in an ID table).

What deficiancy in the current id tables do you see?  What driver has a
id table that is "too big"?  Is there some way we can change it to make
it work better?

thanks,

greg k-h

  parent reply	other threads:[~2005-02-10 18:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 22:30 [RFC][PATCH] add driver matching priorities Adam Belay
2005-01-28 23:23 ` Dmitry Torokhov
2005-01-28 23:33   ` Adam Belay
2005-01-28 23:51     ` Dmitry Torokhov
2005-01-29  0:05       ` Adam Belay
2005-01-29  0:11   ` Al Viro
2005-01-29  2:45     ` Dmitry Torokhov
2005-02-10  8:41 ` Greg KH
2005-02-10 17:18   ` Adam Belay
2005-02-10 18:08     ` Dmitry Torokhov
2005-02-10 18:12     ` Greg KH
2005-02-10 21:26       ` Adam Belay
2005-02-10 18:33     ` Greg KH [this message]
2005-02-10 18:46       ` Dmitry Torokhov
2005-02-10 21:32         ` Adam Belay
2005-02-10 18:45     ` Russell King
2005-02-10 21:37       ` Adam Belay
2005-02-25 23:41         ` Greg KH
2005-03-01  0:05           ` Adam Belay
2005-03-01  7:58             ` Greg KH

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=20050210183338.GA9308@kroah.com \
    --to=greg@kroah.com \
    --cc=abelay@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.