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: Thu, 4 Mar 2010 02:17:13 +0100 (CET) From: Thomas Gleixner <tglx@...utronix.de> To: Andrew Morton <akpm@...ux-foundation.org> cc: Pavel Machek <pavel@....cz>, Ingo Molnar <mingo@...e.hu>, "Rafael J. Wysocki" <rjw@...k.pl>, Stephen Rothwell <sfr@...b.auug.org.au>, mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org, roland@...hat.com, suresh.b.siddha@...el.com, hjl.tools@...il.com, Linus <torvalds@...ux-foundation.org> Subject: Re: linux-next requirements On Wed, 3 Mar 2010, Andrew Morton wrote: > On Thu, 4 Mar 2010 01:35:43 +0100 (CET) Thomas Gleixner <tglx@...utronix.de> wrote: > > > As a side note: We created checkpatch.pl, to have a tool which helps > > us to alert developers about stuff which is deprecated and as a > > byproduct the coding style rules. I think it's a useful tool in > > general, just the outcome is an utter trainwreck: > > > > We have hordes of whitespace, spelling and codingstyle cleanup > > maniacs, while the hard stuff of replacing deprecated interfaces like > > semaphore based mutexes / completions, cleaning up the BKL horror, > > etc. is left to a few already overworked people who care. > > > > What's even worse is it that developers of new code and the > > maintainers who are merging it simply ignore its existance for > > whatever reasons. I can accept the whitespace argument, but I have no > > grasp why deprecation warnings are ignored at will. > > um, write checkpatch rules to detect new additions of deprecated features. > > I take patches. Guess what ? There are rules already which warn about init_MUTEX, init_MUTEX_locked for quite a while and that's why I'm ranting at both developers and maintainers submitting resp. merging code containing exactly that shit. But yeah we do not have one for lock/unlock_kernel, will send one. Thanks, tglx -- 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