From: Chuck Ebbert <cebbert@redhat.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Greg KH <greg@kroah.com>, Chris Wright <chrisw@sous-sol.org>
Subject: [stable] Wanted: Allow adding new device IDs during the -stable cycle
Date: Tue, 22 May 2007 14:14:44 -0400 [thread overview]
Message-ID: <46533314.10206@redhat.com> (raw)
I'd like to propose we allow adding new device IDs as part
of the -stable process, but only under certain conditions:
1) Each device (or group of devices) gets added as a separate
patch, i.e. we don't just diff the device tables. This way
each original patch that added the device(s) upstream will
be become a single patch for -stable.
2) Devices that require new features/capabilities in their
driver won't be added.
Candidate patches would be something like these, which together
add support for the ATI SB700 ATA controller:
1)
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=823777181b4c0200923dcb026efa5b37f55c0ecf
Adds ATI sb700 quirk, using exactly the same one as sb600.
2)
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2bcfdde6767f2f07891d2753c25220012fe5e6d2
Adds the new device to the existing driver's device ID table.
next reply other threads:[~2007-05-22 18:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 18:14 Chuck Ebbert [this message]
2007-05-22 18:47 ` [stable] Wanted: Allow adding new device IDs during the -stable cycle 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
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=46533314.10206@redhat.com \
--to=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.