| 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: Fri, 28 Sep 2007 11:06:09 +0200 From: Thomas Gleixner <tglx@...utronix.de> To: Andy Whitcroft <apw@...dowen.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, roel <12o3l@...cali.nl>, lkml <linux-kernel@...r.kernel.org>, Randy Dunlap <rdunlap@...otime.net>, Ingo Molnar <mingo@...e.hu> Subject: Re: [PATCH] spin_lock_unlocked cleanups On Fri, 2007-09-28 at 09:56 +0100, Andy Whitcroft wrote: > > > I think we're ready to wire checkpatch up to a email robot which monitors > > > the mailing lists and sends people nastygrams. I bet that'll be popular ;) > > > > We should wire it up to git-commit as well. A lot of that comes in via > > git subsystems. > > The problem with git-commit is who's repo to add the hook to. I did > attempt to do this by picking up each of linus' main releases and then > using the git blame engine to attribute each "failure" to a particular > commit. The plan then would be to send a nasty-gram to the committer > about violations there-in. > > I'll try and find some time to get this bit polished and at least > emailing me. The question is, whether we can convince the git developers to integrate it. When a commit happens and checkpatch.pl is in scripts/, then run the patch through it before doing the actual commit. 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