| 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: Sat, 23 Feb 2008 15:25:24 -0500 From: Jeff Garzik <jeff@...zik.org> To: James Bottomley <James.Bottomley@...senPartnership.com>, Linus Torvalds <torvalds@...ux-foundation.org> CC: Andrew Morton <akpm@...ux-foundation.org>, linux-scsi <linux-scsi@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [GIT PATCH] scsi fixes for 2.6.25-rc2 James Bottomley wrote: > This is the latest crop of bug fixes plus one new driver: mvsas. We're [...] > Jeff Garzik (1): > mvsas: Add Marvell 6440 SAS/SATA driver [...] > Ke Wei (1): > mvsas: convert from rough draft to working driver I know I am probably shooting myself in the foot here, since I am the original author of mvsas, but... Should we be adding new drivers during -rc? On one hand, it's clear the addition does not break anything, and adds value for users. On the other hand, it's clearly not a bug fix, and -rc could easily get bloated with new drivers that didn't make the merge window. On the net driver side of things, I have a few new net drivers that I have queued for 2.6.26, because they did not make the merge window. This is inconsistent with your apparently policy. I would just prefer to have a clear and consistent policy here, regarding new drivers during -rc. Thanks, Jeff -- 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