public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: David Hollis <dhollis@davehollis.com>
Cc: Greg KH <greg@kroah.com>, Dave Jones <davej@redhat.com>,
	Chuck Ebbert <cebbert@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [stable] Wanted: Allow adding new device IDs during the	-stable cycle
Date: Thu, 24 May 2007 16:44:34 -0400	[thread overview]
Message-ID: <4655F932.20006@garzik.org> (raw)
In-Reply-To: <1179969655.4489.3.camel@dhollis-lnx.sunera.com>

David Hollis wrote:
> With the asix.c driver, you can't just add the USB IDs and have it work.
> Each ID also needs to be told which driver structure to use, since the
> driver itself supports three similar, but distinct chips.  Adding the
> IDs to the driver itself is naturally trivial, but adding via sysfs or
> the like doesn't work.  I would imagine that there are other drivers
> that operate quite similarly.

As is evident from the patches that do upstream (a requirement for 
-stable), it depends on the driver.  Some drivers work just fine with a 
simple ID addition.

Review the thread, we are just talking about the patches where adding an 
ID is the only work necessary.

	Jeff



  reply	other threads:[~2007-05-24 20:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 18:14 [stable] Wanted: Allow adding new device IDs during the -stable cycle Chuck Ebbert
2007-05-22 18:47 ` Greg KH
2007-05-22 18:53   ` Dave Jones
2007-05-22 19:36     ` Greg KH
2007-05-22 19:04   ` Jeff Garzik
2007-05-22 19:35     ` Greg KH
2007-05-22 19:51       ` Dave Jones
2007-05-22 22:17         ` Greg KH
2007-05-22 22:56           ` Dave Jones
2007-05-23  0:06             ` Greg KH
2007-05-24  1:20           ` David Hollis
2007-05-24 20:44             ` Jeff Garzik [this message]
2007-05-22 20:24       ` Jeff Garzik
2007-05-22 22:15         ` Greg KH
2007-05-22 22:00       ` Chris Wright
2007-05-22 22:19         ` Greg KH
2007-05-22 22:47         ` Jeff Garzik
2007-05-23  0:25           ` Chris Wright
2007-05-24 10:04     ` Pavel Machek
2007-05-24 10:06       ` Jeff Garzik
2007-05-25  6:46         ` Pavel Machek

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=4655F932.20006@garzik.org \
    --to=jeff@garzik.org \
    --cc=cebbert@redhat.com \
    --cc=chrisw@sous-sol.org \
    --cc=davej@redhat.com \
    --cc=dhollis@davehollis.com \
    --cc=greg@kroah.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