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
Date: Thu, 4 Jan 2018 09:29:48 +0530 [thread overview]
Message-ID: <20180104035948.GB3782@afzalpc> (raw)
In-Reply-To: <20180104014850.GB31392@tardis>
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
next prev parent reply other threads:[~2018-01-04 4:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 9:34 [PATCH] doc: memory-barriers: reStructure Text afzal mohammed
2018-01-03 23:48 ` Peter Zijlstra
2018-01-04 3:43 ` afzal mohammed
2018-01-04 1:48 ` Boqun Feng
2018-01-04 3:59 ` afzal mohammed [this message]
2018-01-04 10:27 ` Markus Heiser
2018-01-05 3:52 ` afzal mohammed
2018-01-05 10:22 ` Markus Heiser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180104035948.GB3782@afzalpc \
--to=afzal.mohd.ma@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=drozdziak1@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mingo@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox