All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 01/12] docs/cpu-hotplug.rst: Fix rST markup issues
Date: Thu,  7 Mar 2019 15:24:39 +0000	[thread overview]
Message-ID: <20190307152450.20340-2-peter.maydell@linaro.org> (raw)
In-Reply-To: <20190307152450.20340-1-peter.maydell@linaro.org>

sphinx-build complains:

docs/cpu-hotplug.rst:67: ERROR: Unexpected indentation.
docs/cpu-hotplug.rst:69: ERROR: Unexpected indentation.
docs/cpu-hotplug.rst:74: WARNING: Block quote ends without a blank line; unexpected unindent.
docs/cpu-hotplug.rst:75: WARNING: Block quote ends without a blank line; unexpected unindent.
docs/cpu-hotplug.rst:76: SEVERE: Unexpected section title.

}
{
docs/cpu-hotplug.rst:78: WARNING: Block quote ends without a blank line; unexpected unindent.

These are the result of not indicating one of the literal
blocks by finishing the preceding paragraph with the "::" marker.

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Acked-by: Aleksandar Markovic <amarkovic@wavecomp.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Cleber Rosa <crosa@redhat.com>
Message-id: 20190305172139.32662-2-peter.maydell@linaro.org
Message-id: 20190228145624.24885-2-peter.maydell@linaro.org
---
 docs/cpu-hotplug.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/cpu-hotplug.rst b/docs/cpu-hotplug.rst
index cfeb79f5711..d0b06403f19 100644
--- a/docs/cpu-hotplug.rst
+++ b/docs/cpu-hotplug.rst
@@ -60,7 +60,7 @@ vCPU hotplug
     hot-plugged (no "qom-path" member).  From its output in step (3), we
     can see that ``IvyBridge-IBRS-x86_64-cpu`` is present in socket 0,
     while hot-plugging a CPU into socket 1 requires passing the listed
-    properties to QMP ``device_add``:
+    properties to QMP ``device_add``::
 
       (QEMU) device_add id=cpu-2 driver=IvyBridge-IBRS-x86_64-cpu socket-id=1 core-id=0 thread-id=0
       {
-- 
2.20.1

  reply	other threads:[~2019-03-07 15:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 15:24 [Qemu-devel] [PULL 00/12] sphinx queue Peter Maydell
2019-03-07 15:24 ` Peter Maydell [this message]
2019-03-07 15:24 ` [Qemu-devel] [PULL 02/12] docs: Convert memory.txt to rst format Peter Maydell
2019-03-07 15:24 ` [Qemu-devel] [PULL 03/12] docs: Commit initial files from sphinx-quickstart Peter Maydell
2019-03-07 15:24 ` [Qemu-devel] [PULL 04/12] docs/conf.py: Disable unused _static directory Peter Maydell
2019-03-07 15:24 ` [Qemu-devel] [PULL 05/12] docs/conf.py: Configure the 'alabaster' theme Peter Maydell
2019-03-07 15:24 ` [Qemu-devel] [PULL 06/12] docs/conf.py: Don't include rST sources in HTML build Peter Maydell
2019-03-07 15:24 ` [Qemu-devel] [PULL 07/12] docs/conf.py: Disable option warnings Peter Maydell
2019-03-07 15:24 ` [Qemu-devel] [PULL 08/12] docs: Provide separate conf.py for each manual we want Peter Maydell
2019-03-07 15:24 ` [Qemu-devel] [PULL 09/12] Makefile, configure: Support building rST documentation Peter Maydell
2019-03-07 15:24 ` [Qemu-devel] [PULL 10/12] Makefile: Abstract out "identify the pkgversion" code Peter Maydell
2019-03-07 15:24 ` [Qemu-devel] [PULL 11/12] docs/conf.py: Don't hard-code QEMU version Peter Maydell
2019-03-07 15:24 ` [Qemu-devel] [PULL 12/12] MAINTAINERS: Add entry for Sphinx documentation infrastructure Peter Maydell
2019-03-07 16:07 ` [Qemu-devel] [PULL 00/12] sphinx queue no-reply
2019-03-07 16:12 ` Peter Maydell
2019-03-08  0:42   ` Philippe Mathieu-Daudé
2019-03-08 10:28     ` Peter Maydell
2019-03-07 16:12 ` no-reply

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=20190307152450.20340-2-peter.maydell@linaro.org \
    --to=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.