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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <19f34abd0804030526j3b54e4a2ya5cd22677721cd08@mail.gmail.com>
Date:	Thu, 3 Apr 2008 14:26:01 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Jörn Engel" <joern@...fs.org>
Cc:	"David Miller" <davem@...emloft.net>, mingo@...e.hu,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 109/148] include/asm-x86/serial.h: checkpatch cleanups - formatting only

Hi,

[Some CCs dropped. I don't think they're truly interested.]

On 3/26/08, Jörn Engel <joern@...fs.org> wrote:
>  What is the reason why (void *)foo is better than (void*)foo?  Just that
>  fact that by random chance one them them became more common in our
>  codebase and the minority always has to give in?

I think the rationale for using (void *) over (void*) is that we
usually write a space before the * in other places (again, it's about
consistency). Or do you also write void*a; in variable declarations?


Vegard

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ