linux-kernel - Re: [PATCH v4 02/28] docs: arm64: convert docs to ReST and rename to .rst

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: <20190614141041.335a76e5@lwn.net>
Date:   Fri, 14 Jun 2019 14:10:41 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
Cc:     Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab@...radead.org>,
        linux-kernel@...r.kernel.org,
        Catalin Marinas <catalin.marinas@....com>,
        Will Deacon <will.deacon@....com>,
        Harry Wei <harryxiyou@...il.com>,
        Alex Shi <alex.shi@...ux.alibaba.com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Radim Krčmář <rkrcmar@...hat.com>,
        Ard Biesheuvel <ard.biesheuvel@...aro.org>,
        linux-arm-kernel@...ts.infradead.org, kvm@...r.kernel.org,
        linux-efi@...r.kernel.org
Subject: Re: [PATCH v4 02/28] docs: arm64: convert docs to ReST and rename
 to .rst

On Wed, 12 Jun 2019 14:52:38 -0300
Mauro Carvalho Chehab <mchehab+samsung@...nel.org> wrote:

> The documentation is in a format that is very close to ReST format.
> 
> The conversion is actually:
>   - add blank lines in order to identify paragraphs;
>   - fixing tables markups;
>   - adding some lists markups;
>   - marking literal blocks;
>   - adjust some title markups.
> 
> At its new index.rst, let's add a :orphan: while this is not linked to
> the main index.rst file, in order to avoid build warnings.

This one doesn't apply to docs-next, since there's a bunch of stuff in
linux-next that I don't have.  I'd suggest that it either go by way of an
ARM tree or send it my way again after the ARM changes go upstream.

Thanks,

jon