public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: 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: Tue, 22 May 2007 12:36:45 -0700	[thread overview]
Message-ID: <20070522193645.GB885@kroah.com> (raw)
In-Reply-To: <20070522185353.GE12157@redhat.com>

On Tue, May 22, 2007 at 02:53:53PM -0400, Dave Jones wrote:
> On Tue, May 22, 2007 at 11:47:33AM -0700, Greg Kroah-Hartman wrote:
>  > On Tue, May 22, 2007 at 02:14:44PM -0400, Chuck Ebbert wrote:
>  > > I'd like to propose we allow adding new device IDs as part
>  > > of the -stable process, but only under certain conditions:
>  > 
>  > Who would be the primary benifactor of this?
>  > 
>  > The very large majority of users out there use a distro kernel, and they
>  > provide the ids whenever possible as patches to their kernels, _or_ as a
>  > config option at startup that adds the ids to the drivers through sysfs.
> 
> It does mean however that there's lots of duplicated work between
> distros as everyone adds these patches anyway.

But distros don't all standardize on the same -stable release anyway, so
I don't see how a large ammount of duplicated work happens here.

>  > What's wrong with the current sysfs way of adding new device ids without
>  > touching the kernel?
> 
> sure, that works in some cases, but for others (quirks etc) it obviously doesn't.

I totally agree, and have never objected to quirk additions in the past.

thanks,

greg k-h

  reply	other threads:[~2007-05-22 19:39 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 [this message]
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
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=20070522193645.GB885@kroah.com \
    --to=greg@kroah.com \
    --cc=cebbert@redhat.com \
    --cc=chrisw@sous-sol.org \
    --cc=davej@redhat.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