| 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, 24 Jul 2006 02:49:57 +0200 (CEST) From: Tomasz Kłoczko <kloczek@...y.mif.pg.gda.pl> To: Michael Buesch <mb@...sch.de> cc: linux-kernel@...r.kernel.org, Alexey Dobriyan <adobriyan@...il.com> Subject: Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc. On Mon, 24 Jul 2006, Tomasz Kłoczko wrote: [..] > In all other/most of cases (probably ~99%) Lindetd can be used .. but for NOW > GENERALY IT IS NOT NOT USED. I'm just look on number changed fles by Lindent. diffstat shows 14593 changed files. Number of all *.[ch] files is 16028. So it shows now ~9% all files passes cleanly indentation using Lindent (my above "GENERALY IT IS NOT NOT USED" isn't true :). IMO it is sill possible add general rule "allways use Lindent" because indent can be dissabled/enabled aroud code inccorectly formated by add control comments like: /* *INDENT-OFF* */ /* *INDENT-ON* */ If it will be widely used probably it will allow better identify some indent problems. kloczek -- ----------------------------------------------------------- *Ludzie nie mają problemów, tylko sobie sami je stwarzają* ----------------------------------------------------------- Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@...y.mif.pg.gda.pl*
Powered by blists - more mailing lists