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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 22 Jul 2006 20:35:11 +0200 (CEST)
From:	Tomasz Kłoczko <kloczek@...y.mif.pg.gda.pl>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	Pekka J Enberg <penberg@...Helsinki.FI>,
	Panagiotis Issaris <takis@....org>,
	Jesper Juhl <jesper.juhl@...il.com>,
	Jeff Garzik <jgarzik@...ox.com>,
	Rolf Eike Beer <eike-kernel@...tec.de>,
	Panagiotis Issaris <takis@...umba.uhasselt.be>,
	linux-kernel@...r.kernel.org, len.brown@...el.com,
	chas@....nrl.navy.mil, miquel@...uba.ar, kkeil@...e.de,
	benh@...nel.crashing.org, video4linux-list@...hat.com,
	rmk+mmc@....linux.org.uk, Neela.Kolli@...enio.com,
	vandrove@...cvut.cz, adaplas@....net, thomas@...ischhofer.net,
	weissg@...nna.at, philb@....org, linux-pcmcia@...ts.infradead.org,
	jkmaline@...hut.fi, paulus@...ba.org
Subject: Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.

On Sat, 22 Jul 2006, Stefan Richter wrote:
[..]
> Style issues like "sizeof(struct foo)" versus "sizeof(*bar)" in memory 
> allocation are beyond what indent can and should do.
>
>> Coding style seems is Linux case kind of never ending story.
>
> It's not a big deal in my limited experience, as far as there is a documented 
> consensus.
>
>> Keep one/common coding style in this case is someting not for small tool 
>> but more for .. Superman/Hecules (?)
> [...]
>
> Yes. Or subsystem maintainers who didn't already could adopt the documented 
> style. Or correct the document where it doesn't reflect consensus.

Moment .. are you want to say something like "keep commont coding style 
can't be maintained by tool" ?
Even if indent watches on to small coding style emenets still I don't see 
why using this tool isn't one of the current ement of release procedure 
(?).

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ