lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 30 Apr 2007 21:58:06 -0700 From: Greg KH <greg@...ah.com> To: Jeff Garzik <jeff@...zik.org> Cc: Chris Wright <chrisw@...s-sol.org>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, stable@...nel.org Subject: Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge plans) On Mon, Apr 30, 2007 at 08:45:25PM -0400, Jeff Garzik wrote: > Chris Wright wrote: > > 2) you can add them > > runtime in userspace (and for pcmcia too after patch in question is > > applied), so we've historically avoided that kind of patch for -stable. > > > Due to distro installer environments, and very poor support for making > dynamic PCI IDs persistent once added, what you describe is more of a > goal than reality. But distros can easily add the device id to their kernel if needed, it isn't something that the -stable tree shoud be accepting. Otherwise, we will be swamped with those types of patches... thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists