[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170515134012.21222-1-j.neuschaefer@gmx.net>
Date: Mon, 15 May 2017 15:40:07 +0200
From: Jonathan Neuschäfer <j.neuschaefer@....net>
To: linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
Jonathan Neuschäfer <j.neuschaefer@....net>
Subject: [PATCH 1/6] Documentation: coding-style: Escape \n\t to fix HTML rendering
Without this patch, Sphinx renders the sentence as follows, thus hiding
the backslashes:
[...] end each string except the last with <cite>nt</cite> to
properly indent the next instruction [...]
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@....net>
---
Documentation/process/coding-style.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
index d20d52a4d812..7710c7e0240c 100644
--- a/Documentation/process/coding-style.rst
+++ b/Documentation/process/coding-style.rst
@@ -980,7 +980,7 @@ do so, though, and doing so unnecessarily can limit optimization.
When writing a single inline assembly statement containing multiple
instructions, put each instruction on a separate line in a separate quoted
-string, and end each string except the last with \n\t to properly indent the
+string, and end each string except the last with ``\n\t`` to properly indent the
next instruction in the assembly output:
.. code-block:: c
--
2.11.0
Powered by blists - more mailing lists