mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Subject: [PATCH 1/6] Documentation: coding-style: Escape \n\t to fix HTML rendering
Date: Mon, 15 May 2017 15:40:07 +0200	[thread overview]
Message-ID: <20170515134012.21222-1-j.neuschaefer@gmx.net> (raw)

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@gmx.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

             reply	other threads:[~2017-05-15 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 13:40 Jonathan Neuschäfer [this message]
2017-05-15 13:40 ` [PATCH 2/6] Documentation: kernel-docs: Move vfs.txt under "Docs at the Linux Kernel tree" Jonathan Neuschäfer
2017-05-15 13:40 ` [PATCH 3/6] Documentation: kernel-docs: Remove "Here is its" at the end of lines Jonathan Neuschäfer
2017-05-15 13:40 ` [PATCH 4/6] Documentation: Remove outdated info about -git patches Jonathan Neuschäfer
2017-05-15 13:40 ` [PATCH 5/6] Documentation: howto: Remove outdated info about bugzilla mailing lists Jonathan Neuschäfer
2017-05-15 13:40 ` [PATCH 6/6] Documentation: mono: Update links and s/CVS/Git/ Jonathan Neuschäfer

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=20170515134012.21222-1-j.neuschaefer@gmx.net \
    --to=j.neuschaefer@gmx.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®