| 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: Mon, 2 Sep 2013 15:08:05 -0700 From: Josh Triplett <josh@...htriplett.org> To: David Howells <dhowells@...hat.com> Cc: Joe Perches <joe@...ches.com>, Andy Whitcroft <apw@...onical.com>, ksummit-2013-discuss@...ts.linuxfoundation.org, Linus Torvalds <torvalds@...ux-foundation.org>, linux-kernel@...r.kernel.org, Mauro Carvalho Chehab <m.chehab@...sung.com> Subject: Re: [Ksummit-2013-discuss] [PATCH] checkpatch: Add comment about updating Documentation/CodingStyle On Mon, Sep 02, 2013 at 09:50:23PM +0100, David Howells wrote: > Josh Triplett <josh@...htriplett.org> wrote: > > > > There are many checkpatch rules (like semicolons) that > > > are not in CodingStyle. > > > > It's a rule of thumb, not a mandate. In *general*, checkpatch.pl should > > not be enforcing style rules that aren't documented in CodingStyle. > > Except that it becomes a mandate when someone runs it automatically against > every one of your patches and then sends you an email for each patch it finds > a checkpatch niggle against... I think we're talking about two different things. I wasn't talking about checkpatch.pl itself; I was talking about the idea that every style rule in checkpatch.pl should corresponding documentation in CodingStyle. That's what I was calling a rule of thumb rather than a mandate. - Josh triplett -- 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