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
| ||
|
Date: Thu, 2 May 2019 09:20:05 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: "Tobin C. Harding" <tobin@...nel.org> Cc: Josh Poimboeuf <jpoimboe@...hat.com>, Jiri Kosina <jikos@...nel.org>, Miroslav Benes <mbenes@...e.cz>, Petr Mladek <pmladek@...e.com>, "Rafael J. Wysocki" <rafael@...nel.org>, Joe Lawrence <joe.lawrence@...hat.com>, live-patching@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [RFC PATCH 3/5] kobject: Fix kernel-doc comment first line On Thu, May 02, 2019 at 12:31:40PM +1000, Tobin C. Harding wrote: > kernel-doc comments have a prescribed format. This includes parenthesis > on the function name. To be _particularly_ correct we should also > capitalise the brief description and terminate it with a period. Ah, I didn't know that, sorry about that, my fault. I'll take patch 2 and 3 now in my tree, thanks! greg k-h
Powered by blists - more mailing lists