From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jeff@garzik.org>
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:15:33 -0700 [thread overview]
Message-ID: <20070522221533.GB2302@kroah.com> (raw)
In-Reply-To: <46535164.8080604@garzik.org>
On Tue, May 22, 2007 at 04:24:04PM -0400, Jeff Garzik wrote:
> Greg KH wrote:
> > Well, SuSE handles this just fine, but I do notice that RHEL 5 disables
> > the new_id stuff entirely, so I can see why you might get this
> > impression :)
>
> I looked at distros other than those produced by my employer.
>
> Apparently you did not.
>
> This is not how we best serve Linux users.
See that ":)" above?
Anyway, I'm pretty sure that Ubuntu also handles new device ids through
sysfs, or so I was told once, but I don't have a box to test that out
on. Oh, and Dell has some userspace tools that also use this interface
for adding new ids.
thanks,
greg k-h
next prev parent reply other threads:[~2007-05-22 22:20 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 [this message]
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=20070522221533.GB2302@kroah.com \
--to=greg@kroah.com \
--cc=cebbert@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=jeff@garzik.org \
--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