From: Chris Wright <chrisw@sous-sol.org>
To: Greg KH <greg@kroah.com>
Cc: Jeff Garzik <jeff@garzik.org>, 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:00:44 -0700 [thread overview]
Message-ID: <20070522220044.GB3429@sequoia.sous-sol.org> (raw)
In-Reply-To: <20070522193538.GA885@kroah.com>
* Greg KH (greg@kroah.com) wrote:
> On Tue, May 22, 2007 at 03:04:08PM -0400, Jeff Garzik wrote:
> > 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?
Yes, we're here to help. The only compelling reasons not do to it were/are:
1) -stable has never been about adding features (easy to consider new
hardware support a feature).
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.
3) It hasn't been a pressing issue brought to our attention until this
thread and its predecessor earlier in the month.
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.
> I'm not disagreeing that it will help a set of users, or that it will
> cause any harm at all. It's just currently outside the scope for what
> we defined -stable as, and it will slightly increase the workload that
> Chris and I have in keeping up with these patches.
>
> So, if there is an overwhelming majority of people that strongly feel
> that this is a good thing, fine, we can try it out.
Yes, if it will serve -stable users better, we can give it a trial run
to see how it goes.
thanks,
-chris
next prev parent reply other threads:[~2007-05-22 22:01 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 [this message]
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=20070522220044.GB3429@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=cebbert@redhat.com \
--cc=greg@kroah.com \
--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