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, 02 Sep 2013 11:59:27 -0700 From: Joe Perches <joe@...ches.com> To: Mauro Carvalho Chehab <m.chehab@...sung.com> Cc: Josh Triplett <josh@...htriplett.org>, linux-kernel@...r.kernel.org, Andy Whitcroft <apw@...onical.com>, Linus Torvalds <torvalds@...ux-foundation.org>, ksummit-2013-discuss@...ts.linuxfoundation.org Subject: Re: [Ksummit-2013-discuss] [PATCH] checkpatch: Add comment about updating Documentation/CodingStyle On Mon, 2013-09-02 at 15:39 -0300, Mauro Carvalho Chehab wrote: > Em Mon, 2 Sep 2013 11:19:01 -0700 > Josh Triplett <josh@...htriplett.org> escreveu: [] > > +# This file does not define the kernel coding style; Documentation/CodingStyle > > +# does. If you add a new style test to this file, add the corresponding style > > +# rule it enforces to Documentation/CodingStyle. > Agreed with that. I do not. > I would also add another comment there: "in case of > conflicts between checkpatch.pl and Documentation/CodingStyle, the latter > takes precedence." There are many checkpatch rules (like semicolons) that are not in CodingStyle. CodingStyle should not become some intensely detailed document that specifies the "only one true way" to write code. I also think checkpatch should not be used by robots to determine that patches are bad or unacceptable. checkpatch is just a dumb little tool that has some utility but as Dan Carpenter once said, "it's less sentient than a squirrel". People should always use their own taste before relying on dumb tools. -- 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