All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Greg KH <greg@kroah.com>, Chuck Ebbert <cebbert@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [stable] Wanted: Allow adding new device IDs during the	-stable cycle
Date: Tue, 22 May 2007 18:47:48 -0400	[thread overview]
Message-ID: <46537314.4080605@garzik.org> (raw)
In-Reply-To: <20070522220044.GB3429@sequoia.sous-sol.org>

Chris Wright wrote:
> 2) In theory new hardware can seem to work with a simple PCI ID
> update, and later we find it needs extra quirk handling or specific
> driver support.  This could mean adding buggy support for new hardware
> to -stable.  In practice, hopefully this isn't a real issue.

No need to worry about theory.  Since you are (or should be???) taking 
stuff solely from upstream, you should already know what is needed, or not.


> 3) It hasn't been a pressing issue brought to our attention until this
> thread and its predecessor earlier in the month.

Search your email archives, it has been brought more than the two times 
you cite.


> My own personal experience is each time I've needed a PCI ID update for
> new hardware it's also needed changes to the driver (read: e1000, every
> single time).  So from my perspective neither sysfs nor relaxing -stable
> rules slightly would actually help provide support for new hardware,
> but that's clearly limited experience.

e1000 is not a representative sample at all...

	Jeff



  parent reply	other threads:[~2007-05-22 22:48 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
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 [this message]
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=46537314.4080605@garzik.org \
    --to=jeff@garzik.org \
    --cc=cebbert@redhat.com \
    --cc=chrisw@sous-sol.org \
    --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 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.