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: <4c566329-b2ce-80a5-00da-f3048bdbed3e@gmail.com>
Date:   Wed, 22 Jun 2022 15:36:14 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Ira Weiny <ira.weiny@...el.com>
Cc:     linux-doc@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        "Matthew Wilcox (Oracle)" <willy@...radead.org>,
        "Fabio M. De Francesco" <fmdefrancesco@...il.com>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] Documentation: highmem: Use literal block for code
 example in highmem.h comment

On 6/21/22 04:44, Ira Weiny wrote:

>> Fix these warnings by indenting the code example with literal block
>> indentation and prefixing comments inside the example with C comment
>> symbol (#).
> 
> "//"?
> 
> Frankly I'd just drop "(#)".
> 
> Perhaps:
> 
> ... indentation and making the comments C comments.
> 

Ah! I had overlooked that. Thanks.

-- 
An old man doll... just what I always wanted! - Clara

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ