From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 1/2] vhost-user: fix indentation in protocol specification
Date: Thu, 14 Dec 2017 20:22:19 +0000 [thread overview]
Message-ID: <20171214202220.20379-2-stefanha@redhat.com> (raw)
In-Reply-To: <20171214202220.20379-1-stefanha@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
docs/interop/vhost-user.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/interop/vhost-user.txt b/docs/interop/vhost-user.txt
index 954771d0d8..fd8ac56562 100644
--- a/docs/interop/vhost-user.txt
+++ b/docs/interop/vhost-user.txt
@@ -53,8 +53,8 @@ Depending on the request type, payload can be:
* A vring state description
---------------
- | index | num |
- ---------------
+ | index | num |
+ ---------------
Index: a 32-bit index
Num: a 32-bit number
--
2.14.3
next prev parent reply other threads:[~2017-12-14 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 20:22 [Qemu-devel] [PATCH 0/2] vhost-user: document memory accesses Stefan Hajnoczi
2017-12-14 20:22 ` Stefan Hajnoczi [this message]
2017-12-14 20:22 ` [Qemu-devel] [PATCH 2/2] " Stefan Hajnoczi
2017-12-19 12:42 ` Maxime Coquelin
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=20171214202220.20379-2-stefanha@redhat.com \
--to=stefanha@redhat.com \
--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 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).