qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [PATCH qemu 1/1] Remove a stray "@end table" marker
  2023-01-26  2:47 [PATCH qemu 0/1] Minor doc patch ~gurjeet
@ 2023-01-26  2:12 ` ~gurjeet
  2023-01-26  3:34   ` Richard Henderson
  0 siblings, 1 reply; 3+ messages in thread
From: ~gurjeet @ 2023-01-26  2:12 UTC (permalink / raw)
  To: qemu-devel; +Cc: Gurjeet, Paolo Bonzini, Richard Henderson, Eduardo Habkost

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


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* [PATCH qemu 0/1] Minor doc patch
@ 2023-01-26  2:47 ~gurjeet
  2023-01-26  2:12 ` [PATCH qemu 1/1] Remove a stray "@end table" marker ~gurjeet
  0 siblings, 1 reply; 3+ messages in thread
From: ~gurjeet @ 2023-01-26  2:47 UTC (permalink / raw)
  To: qemu-devel; +Cc: Gurjeet, Paolo Bonzini, Richard Henderson, Eduardo Habkost

PS: Sorry for the duplicate email; I forgot to CC myself the last time.
I'm using Sourcehut's web-based send-email, as recommended in
submitting-a-patch.html#submitting-your-patches docs.

Gurjeet Singh (1):
  Remove a stray "@end table" marker

 docs/system/cpu-models-x86.rst.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.34.5


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH qemu 1/1] Remove a stray "@end table" marker
  2023-01-26  2:12 ` [PATCH qemu 1/1] Remove a stray "@end table" marker ~gurjeet
@ 2023-01-26  3:34   ` Richard Henderson
  0 siblings, 0 replies; 3+ messages in thread
From: Richard Henderson @ 2023-01-26  3:34 UTC (permalink / raw)
  To: ~gurjeet, qemu-devel; +Cc: Paolo Bonzini, Eduardo Habkost, qemu-trivial

On 1/25/23 16:12, ~gurjeet wrote:
> 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.

Cc: qemu-trivial.

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

r~


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-01-26  8:31 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-01-26  2:47 [PATCH qemu 0/1] Minor doc patch ~gurjeet
2023-01-26  2:12 ` [PATCH qemu 1/1] Remove a stray "@end table" marker ~gurjeet
2023-01-26  3:34   ` Richard Henderson

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).