linux-kernel - Re: [PATCH v2 1/1] net: Fix comment block per style guide

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] [day] [month] [year] [list]

Message-Id: <20191118.164712.488135429319455452.davem@davemloft.net>
Date:   Mon, 18 Nov 2019 16:47:12 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     tdavies@...kphysics.net
Cc:     akpm@...ux-foundation.org, julia.lawall@...6.fr,
        kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/1] net: Fix comment block per style guide

From: Travis Davies <tdavies@...kphysics.net>
Date: Mon, 18 Nov 2019 14:06:09 -0800

> This patch places /* and */ on separate lines for a
> multiline block comment, in order to keep code style
> consistant with majority of blocks throughout the file.
> 
> This will prevent a checkpatch.pl warning:
> 'Block comments use a trailing */ on a separate line'
> 
> Signed-off-by: Travis Davies <tdavies@...kphysics.net>
> ---
> -v2: Fix commit description, and subject line as suggested by 
>      Julie Lawall

The comment style used here is so pervasive in the kernel networking,
I'm really not thrilled to start seeing these picked away one by
one.  So much churn...

Sorry I'm not applying this...