linux-kernel - Re: [PATCH v2 7/7] docs: put atomic*.txt and memory-barriers.txt into the core-api book

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bad0b6f9-2be9-ef82-86dd-466a89e14507@gmail.com>
Date:   Sun, 25 Sep 2022 10:52:53 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Randy Dunlap <rdunlap@...radead.org>,
        Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org,
        Thorsten Leemhuis <linux@...mhuis.info>,
        Kees Cook <keescook@...omium.org>,
        Jani Nikula <jani.nikula@...ux.intel.com>
Subject: Re: [PATCH v2 7/7] docs: put atomic*.txt and memory-barriers.txt into
 the core-api book

On 9/25/22 10:48, Randy Dunlap wrote:
> 
> 
> On 9/24/22 20:18, Bagas Sanjaya wrote:
>> On 9/23/22 20:39, Jonathan Corbet wrote:
>>>> Shouldn't warning like "This documentation isn't in RST format and included
>>>> as literal block" be added?
>>>
>>> Why?  Who needs that information and what will they do with it?
>>
>> At least readers will not be surprised with the anomaly...
>>
>> But anyway, for consistency, I'd like to see these *.txt docs be converted
>> to proper RST.
> 
> I'm pretty sure that Jonathan knows that those files' owner(s) want them
> to remain in txt format.
> 

OK, thanks!

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