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: <0c433f0a-3ae5-1956-988c-9f4dfdb79fbc@gmail.com>
Date:   Mon, 18 Jan 2021 10:35:26 +0000
From:   Daniel Scally <djrscally@...il.com>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Sakari Ailus <sakari.ailus@...ux.intel.com>
Cc:     gregkh@...uxfoundation.org, rafael@...nel.org,
        linux-kernel@...r.kernel.org, heikki.krogerus@...ux.intel.com
Subject: Re: [PATCH v2] software_node: Add kernel-doc comments to exported
 symbols

On 18/01/2021 10:33, Andy Shevchenko wrote:
> On Mon, Jan 18, 2021 at 11:49:46AM +0200, Sakari Ailus wrote:
>> On Wed, Jan 13, 2021 at 12:02:09AM +0000, Daniel Scally wrote:
>>> + * to_software_node() - Fetch software node associated with a firmware node handle
>> Please wrap lines over 80 (unless there's a reason to keep them longer).
> Does kernel-doc behave good when you wrap the function summary line?
> My impression that summary should be one line.
>
Same, but I can shorten the line by s/associated with/linked to or
something along those lines

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ