linux-kernel - Re: [PATCH 1/9] CodingStyle: make Documentation/CodingStyle into symlink

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: <77f03295-df5d-4bc0-9a61-5be829969662@p183>
Date: Mon, 12 May 2025 19:08:53 +0300
From: Alexey Dobriyan <adobriyan@...il.com>
To: Jonathan Corbet <corbet@....net>
Cc: workflows@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/9] CodingStyle: make Documentation/CodingStyle into
 symlink

On Sat, May 10, 2025 at 04:05:29AM -0600, Jonathan Corbet wrote:
> Alexey Dobriyan <adobriyan@...il.com> writes:
> 
> > Every time I open Documentation/CodingStyle it says the party moved
> > somewhere else. :-(
> >
> > Of course, I forget where it moved to by the next time.
> >
> > Signed-off-by: Alexey Dobriyan <adobriyan@...il.com>
> > ---
> 
> No 0/9 cover letter?

Not really. Cover letter would be very short:

	Tweak coding style to add things I've learned over the years of
	Linux/C programming.

	And stop making kernel devs look like aliens from another Universe
	(see static_assert() rule and especially(!) "declare ALAP" rule)

> Just FYI, I won't apply coding-style patches without a strong sense that
> there is a consensus behind them...I suspect that could prove to be a
> high bar here.

I split them like referendum ballots to see where the consensus at and
not have big single discussion thread.