From: Boqun Feng <boqun.feng@gmail.com>
To: afzal mohammed <afzal.mohd.ma@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:48:50 +0800 [thread overview]
Message-ID: <20180104014850.GB31392@tardis> (raw)
In-Reply-To: <20180103093436.16704-1-afzal.mohd.ma@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
On Wed, Jan 03, 2018 at 03:04:36PM +0530, afzal mohammed wrote:
> Let PDF & HTML's be created out of memory-barriers Text by
> reStructuring.
>
> reStructuring done were,
> 1. Section headers modification, lower header case except start
> 2. Removal of manual index(contents section), since it now gets created
> automatically for html/pdf
> 3. Internal cross reference for easy navigation
> 4. Alignment adjustments
> 5. Strong emphasis made wherever there was emphasis earlier (through
> other ways), strong was chosen as normal emphasis showed in italics,
> which was felt to be not enough & strong showed it in bold
> 6. ASCII text & code snippets in literal blocks
> 7. Backquotes for inline instances in the paragraph's where they are
> expressed not in English, but in C, pseudo-code, file path etc.
> 8. Notes section created out of the earlier notes
> 9. Manual numbering replaced by auto-numbering
> 10.Bibliography (References section) made such that it can be
> cross-linked
>
> Signed-off-by: afzal mohammed <afzal.mohd.ma@gmail.com>
> ---
>
> Hi,
>
> With this change, pdf & html could be generated. There certainly are
> improvements to be made, but thought of first knowing whether migrating
> memory-barriers from txt to rst is welcome.
>
> 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.
Regards,
Boqun
> afzal
>
>
[...]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-01-04 1:46 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 [this message]
2018-01-04 3:59 ` afzal mohammed
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=20180104014850.GB31392@tardis \
--to=boqun.feng@gmail.com \
--cc=afzal.mohd.ma@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