linux-kernel - Re: [PATCH v2 2/4] PCI: Cleanup comments in setup-bus.c to meet kernel coding style guidelines

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]

Date:   Wed, 10 Apr 2019 17:06:03 -0500
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Nicholas Johnson <nicholas.johnson-opensource@...look.com.au>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com>,
        "corbet@....net" <corbet@....net>
Subject: Re: [PATCH v2 2/4] PCI: Cleanup comments in setup-bus.c to meet
 kernel coding style guidelines

Hi Nicholas,

On Mon, Mar 11, 2019 at 04:23:23PM +0000, Nicholas Johnson wrote:
> Change block comments to accepted style with asterisks on each line.
> 
> Justify block comments to 80-character limit to reduce the number of
> lines where possible.

Thanks for doing this; I do accept cleanup patches like this.  It does
simplify things if they are last in a series because that makes it
less likely that the "real" patches will cause conflicts.

Don't repost this series just to fix that; I fixed the (trivial)
conflict by hand already.  Just FYI for the future :)

Bjorn