Date: Thu, 4 Jan 2018 09:29:48 +0530
From: afzal mohammed <afzal.mohd.ma@gmail.com>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
        "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
        Will Deacon <will.deacon@arm.com>,
        Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        Stan Drozd <drozdziak1@gmail.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Mauro Carvalho Chehab <mchehab@kernel.org>,
        Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] doc: memory-barriers: reStructure Text
Message-ID: <20180104035948.GB3782@afzalpc>
References: <20180103093436.16704-1-afzal.mohd.ma@gmail.com>
 <20180104014850.GB31392@tardis>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180104014850.GB31392@tardis>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org

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