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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 02 Oct 2021 08:21:58 -0700
From:   Joe Perches <>
To:     Greg KH <>,
        Nick Desaulniers <>
Cc:     Kees Cook <>,
        Linus Torvalds <>,
        Miguel Ojeda <>,
        Jonathan Corbet <>,
        Randy Dunlap <>,
        Alexey Dobriyan <>,
        Rasmus Villemoes <>,
        Andrew Morton <>,,,
Subject: Re: [PATCH v4] docs: Explain the desired position of function

On Sat, 2021-10-02 at 08:31 +0200, Greg KH wrote:
> I would think that now we have a format that the tools can
> actually follow, while before it was semi-random as to what to pick as
> the "one true way".

There will never be 'one true (and universal) way'.

Most existing code doesn't follow the suggested formatting and you
can't require or expect the existing code to change.

If automated scripts exist to change all the code to that new
'one true way', it wouldn't be applied.
> What am I missing here?

Try writing a regex for the proposal and make sure to separate out
all the various __<foo> attributes into their proper locations...

yuck and g'luck.

Powered by blists - more mailing lists