From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: patches@linaro.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [Qemu-devel] [PATCH v2 01/11] docs/cpu-hotplug.rst: Fix rST markup issues
Date: Thu, 28 Feb 2019 14:56:14 +0000 [thread overview]
Message-ID: <20190228145624.24885-2-peter.maydell@linaro.org> (raw)
In-Reply-To: <20190228145624.24885-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>
---
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 1c268e00b41..e2d4e893b01 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
next prev parent reply other threads:[~2019-02-28 14:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 14:56 [Qemu-devel] [PATCH v2 00/11] Enable build and install of our rST docs Peter Maydell
2019-02-28 14:56 ` Peter Maydell [this message]
2019-02-28 16:14 ` [Qemu-devel] [PATCH v2 01/11] docs/cpu-hotplug.rst: Fix rST markup issues Philippe Mathieu-Daudé
2019-02-28 16:34 ` Peter Maydell
2019-02-28 14:56 ` [Qemu-devel] [PATCH v2 02/11] docs: Convert memory.txt to rst format Peter Maydell
2019-02-28 14:56 ` [Qemu-devel] [PATCH v2 03/11] docs: Commit initial files from sphinx-quickstart Peter Maydell
2019-02-28 16:01 ` Philippe Mathieu-Daudé
2019-02-28 16:27 ` Peter Maydell
2019-02-28 14:56 ` [Qemu-devel] [PATCH v2 04/11] docs/conf.py: Disable unused _static directory Peter Maydell
2019-02-28 14:56 ` [Qemu-devel] [PATCH v2 05/11] docs/conf.py: Configure the 'alabaster' theme Peter Maydell
2019-02-28 14:56 ` [Qemu-devel] [PATCH v2 06/11] docs/conf.py: Don't include rST sources in HTML build Peter Maydell
2019-02-28 14:56 ` [Qemu-devel] [PATCH v2 07/11] docs/conf.py: Disable option warnings Peter Maydell
2019-02-28 14:56 ` [Qemu-devel] [PATCH v2 08/11] docs: Provide separate conf.py for each manual we want Peter Maydell
2019-02-28 14:56 ` [Qemu-devel] [PATCH v2 09/11] Makefile, configure: Support building rST documentation Peter Maydell
2019-02-28 15:49 ` Philippe Mathieu-Daudé
2019-02-28 16:25 ` Peter Maydell
2019-03-05 12:47 ` Peter Maydell
2019-03-05 15:24 ` Peter Maydell
2019-03-06 10:53 ` Paolo Bonzini
2019-02-28 14:56 ` [Qemu-devel] [PATCH v2 10/11] Makefile: Abstract out "identify the pkgversion" code Peter Maydell
2019-02-28 14:56 ` [Qemu-devel] [PATCH v2 11/11] docs/conf.py: Don't hard-code QEMU version Peter Maydell
2019-02-28 15:55 ` Philippe Mathieu-Daudé
2019-02-28 15:15 ` [Qemu-devel] [PATCH v2 00/11] Enable build and install of our rST docs no-reply
2019-02-28 15:34 ` no-reply
2019-02-28 15:50 ` Aleksandar Markovic
2019-02-28 15:53 ` no-reply
2019-02-28 15:59 ` no-reply
2019-02-28 16:18 ` 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=20190228145624.24885-2-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).