| 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
| ||
|
Message-ID: <alpine.LFD.2.01.0910081255510.3432@localhost.localdomain> Date: Thu, 8 Oct 2009 13:00:58 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: James Bottomley <James.Bottomley@...e.de> cc: Andrew Morton <akpm@...ux-foundation.org>, linux-scsi <linux-scsi@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [GIT PULL] SCSI fixes for 2.6.32-rc3 On Thu, 8 Oct 2009, Linus Torvalds wrote: > > What part of "sure, I'll take new drivers after the merge window, but COME > &*^@ ON!" do you have trouble understanding? Put another way: look at the drivers/staging tree. Look at when it gets merged. Do this: git diff --stat v2.6.31-rc1..v2.6.31 drivers/staging/ and then do this: git diff --stat v2.6.30..v2.6.31-rc1 drivers/staging/ adn thing about the fact that they are _all_ "new drivers". Then consider the issue of "merge window" vs "not merge window". It really boils down to the fact that I'm perfectly happy to let new drivers slip in after the merge window in order to help end users. But really - there has to be a limit to it. Not just anything. It has to help end users, and dammit, you have to admit that 50 kloc is damn well not just "another random driver". Linus -- 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