| 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: <20080514145526.GB6569@ucw.cz> Date: Wed, 14 May 2008 16:55:26 +0200 From: Pavel Machek <pavel@....cz> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Adrian Bunk <bunk@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, rjw@...k.pl, davem@...emloft.net, linux-kernel@...r.kernel.org, jirislaby@...il.com Subject: Re: Slow DOWN, please!!! Hi! > > I am saying that it was merged too early, and that there are points that > > should have been addressed before the driver got merged. > > > > Get it submitted for review to linux-kernel. > > Give the maintainers some time to incorporate all comments. > > Even one month later it could still have made it into 2.6.25. > > > > The only problem with my suggestion is that it's currently pretty random > > whether someone takes the time to review such a driver on linux-kernel. > > Now, I do agree that we could/should have some more process in general. I > really _would_ like to have a process in place that basically says: > > - everything must have gone through lkml at least once What about 'must go through lkml at least once *outside the merge window*'. Or is it just me? During the merge window, I'm totally overloaded by all those patches going in and related lkml traffic... -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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