public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Greg KH <greg@kroah.com>
Cc: 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: Tue, 22 May 2007 15:04:08 -0400	[thread overview]
Message-ID: <46533EA8.7020602@garzik.org> (raw)
In-Reply-To: <20070522184733.GA9357@kroah.com>

Greg KH wrote:
> What's wrong with the current sysfs way of adding new device ids without
> touching the kernel?  Devices described above was the very reason we
> added that functionality, so users would not have to constantly update
> their kernel.  The distros provide userspace tools that enable these ids
> to be added and at boot time, everything "just works" properly.

I haven't found a single distro that (a) makes it trivial to add PCI IDs 
at install time, and then (b) ensures those PCI IDs remain persistent 
for each boot.  We are not at all to the "just works" stage yet.

> So, because of that, I don't really see a need to be adding new device
> ids to the -stable tree.

Maybe you are just not seeing all the developers that keep bringing this 
up??

Really, it is just silly to think that one-line PCI IDs patches will 
cause any harm at all, and it should be self-evident that there is clear 
potential to HELP Linux users.  That's why we're all here, right?

	Jeff



  parent reply	other threads:[~2007-05-22 19:04 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 [this message]
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
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=46533EA8.7020602@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox