linux-kernel - Re: [PATCH] doc: memory-barriers: reStructure Text

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: <20180104035948.GB3782@afzalpc>
Date:   Thu, 4 Jan 2018 09:29:48 +0530
From:   afzal mohammed <afzal.mohd.ma@...il.com>
To:     Boqun Feng <boqun.feng@...il.com>
Cc:     linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
        "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
        Will Deacon <will.deacon@....com>,
        Ingo Molnar <mingo@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Stan Drozd <drozdziak1@...il.com>,
        Palmer Dabbelt <palmer@...belt.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH] doc: memory-barriers: reStructure Text

Hi,

On Thu, Jan 04, 2018 at 09:48:50AM +0800, Boqun Feng wrote:

> > The location chosen is "Documentation/kernel-hacking", i was unsure
> > where this should reside & there was no .rst file in top-level directory
> > "Documentation", so put it into one of the existing folder that seemed
> > to me as not that unsuitable.
> > 
> > Other files refer to memory-barrier.txt, those also needs to be
> > adjusted based on where .rst can reside.

> How do you plan to handle the external references? For example, the
> following LWN articles has a link this file:
> 
> 	https://lwn.net/Articles/718628/
> 
> And changing the name and/or location will break that link, AFAIK.

If necessary to handle these, symlink might help here i believe.

Upon trying to understand memory-barriers.txt, i felt that it might be
better to have it in PDF/HTML format, thus attempted to convert it to
rst. And i see it not being welcomed, hence shelving the conversion.

afzal