From: ~gurjeet <gurjeet@git.sr.ht>
To: qemu-devel@nongnu.org
Cc: Gurjeet <gurjeet@singh.im>, Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>
Subject: [PATCH qemu 1/1] Remove a stray "@end table" marker
Date: Wed, 25 Jan 2023 18:12:05 -0800 [thread overview]
Message-ID: <167470125128.13083.10933855577484761075-1@git.sr.ht> (raw)
In-Reply-To: <167470125128.13083.10933855577484761075-0@git.sr.ht>
From: Gurjeet Singh <gurjeet@singh.im>
Signed-off-by: Gurjeet Singh <gurjeet@singh.im>
---
docs/system/cpu-models-x86.rst.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/system/cpu-models-x86.rst.inc b/docs/system/cpu-models-x86.rst.inc
index 7f6368f999..261da6e21d 100644
--- a/docs/system/cpu-models-x86.rst.inc
+++ b/docs/system/cpu-models-x86.rst.inc
@@ -25,7 +25,7 @@ Two ways to configure CPU models with QEMU / KVM
typically refer to specific generations of hardware released by
Intel and AMD. These allow the guest VMs to have a degree of
isolation from the host CPU, allowing greater flexibility in live
- migrating between hosts with differing hardware. @end table
+ migrating between hosts with differing hardware.
In both cases, it is possible to optionally add or remove individual CPU
features, to alter what is presented to the guest by default.
--
2.34.5
next prev parent reply other threads:[~2023-01-26 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 2:47 [PATCH qemu 0/1] Minor doc patch ~gurjeet
2023-01-26 2:12 ` ~gurjeet [this message]
2023-01-26 3:34 ` [PATCH qemu 1/1] Remove a stray "@end table" marker Richard Henderson
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=167470125128.13083.10933855577484761075-1@git.sr.ht \
--to=gurjeet@git.sr.ht \
--cc=eduardo@habkost.net \
--cc=gurjeet@singh.im \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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.