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] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a66qp5vn.fsf@meer.lwn.net>
Date:   Fri, 23 Sep 2022 07:39:08 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Bagas Sanjaya <bagasdotme@...il.com>, 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

Bagas Sanjaya <bagasdotme@...il.com> writes:

> On 9/23/22 03:41, Jonathan Corbet wrote:
>> @@ -0,0 +1,18 @@
>> +.. SPDX-License-Identifier: GPL-2.0
>> +   This is a simple wrapper to bring atomic_bitops.txt into the RST world
>> +   until such a time as that file can be converted directly.
>> +
>> +=============
>> +Atomic bitops
>> +=============
>> +
>> +.. raw:: latex
>> +
>> +    \footnotesize
>> +
>> +.. include:: ../../atomic_bitops.txt
>> +   :literal:
>> +
>> +.. raw:: latex
>> +
>> +    \normalsize
>
> 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?

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ