linux-kernel - Re: [PATCH 109/148] include/asm-x86/serial.h: checkpatch cleanups

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]

Message-ID: <87a5b0800803260503g3a2ab9a4t916239574cd35ddf@mail.gmail.com>
Date:	Wed, 26 Mar 2008 12:03:39 +0000
From:	"Will Newton" <will.newton@...il.com>
To:	"Jörn Engel" <joern@...fs.org>
Cc:	"David Miller" <davem@...emloft.net>, mingo@...e.hu,
	apw@...dowen.org, jirislaby@...il.com, viro@...iv.linux.org.uk,
	joe@...ches.com, tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 109/148] include/asm-x86/serial.h: checkpatch cleanups - formatting only

On Wed, Mar 26, 2008 at 11:58 AM, 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?

It doesn't matter. This is the crux of all interminable coding style
discussions. There is no objectively best coding style. Pick one,
stick to it. That's all that matters.

Linux happens to have a particular coding style, GNU has another. When
I hack Linux code I use one style, when I hack GNU coee I use another.
Arguing about it is a waste of time.
--
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/