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]
Date:   Fri, 3 May 2019 06:23:20 -0600
From:   Jonathan Corbet <>
To:     Randy Dunlap <>
Cc:     "Tobin C. Harding" <>, Johan Hovold <>,
        "Tobin C. Harding" <>,
        Josh Poimboeuf <>,
        Jiri Kosina <>,
        Miroslav Benes <>,
        Petr Mladek <>,
        Greg Kroah-Hartman <>,
        "Rafael J. Wysocki" <>,
        Joe Lawrence <>,,
Subject: Re: [RFC PATCH 3/5] kobject: Fix kernel-doc comment first line

On Thu, 2 May 2019 18:46:16 -0700
Randy Dunlap <> wrote:

> I have seen this discussion before also.  And sometimes it is not even
> a discussion -- it's more of an edict.  To which I object/disagree.
> The current (or past) comment style is perfectly fine IMO.
> No caps needed.  No ending '.' needed.

For however much this matters...I really don't see that there needs to be
a rule one way or the other on this; the documentation serves its purpose
either way.  I guess I see it like "British or American spelling";
there's nothing to drive a conversion in either direction.


Powered by blists - more mailing lists