All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Thomas Huth <thuth@redhat.com>,
	 qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [PATCH trivial 06/21] docs/devel/migration.rst: spelling fix: doen't
Date: Thu, 16 Nov 2023 15:27:41 +0100	[thread overview]
Message-ID: <87a5rdrcwy.fsf@secure.mitica> (raw)
In-Reply-To: <7259b384-cc7f-4400-9891-83e656765ce2@tls.msk.ru> (Michael Tokarev's message of "Wed, 15 Nov 2023 09:41:45 +0300")

Michael Tokarev <mjt@tls.msk.ru> wrote:
> 14.11.2023 22:05, Thomas Huth wrote:
>> On 14/11/2023 17.58, Michael Tokarev wrote:
>>> Fixes: 1aefe2ca1423 "migration/doc: Add documentation for backwards compatiblity"
>>> Cc: Juan Quintela <quintela@redhat.com>
>>> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
>>> ---
>>>   docs/devel/migration.rst | 8 ++++----
>>>   1 file changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/docs/devel/migration.rst b/docs/devel/migration.rst
>>> index 5adf4f12f7..51b1f61f5e 100644
>>> --- a/docs/devel/migration.rst
>>> +++ b/docs/devel/migration.rst
>>> @@ -1061,7 +1061,7 @@ QEMU version, in this case pc-5.1.
>>>   4 - qemu-5.1 -M pc-5.2  -> migrates to -> qemu-5.1 -M pc-5.2
>>> -  This combination is not possible as the qemu-5.1 doen't understand
>>> +  This combination is not possible as the qemu-5.1 does't understand
>> You replaced one typo with another one :-)
>
> Heh. Lovely! :)
>
> The "really-really-fixed" one (without resending):
>
> -  This combination is not possible as the qemu-5.1 doen't understand
> +  This combination is not possible as the qemu-5.1 doesn't understand
>    pc-5.2 machine type.  So nothing to worry here.
>
> ;)
>
> Thank you for the review and for spotting it!
>
> /mjt

Reviewed-by: Juan Quintela <quintela@redhat.com>
with the change.



  parent reply	other threads:[~2023-11-16 14:27 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 16:58 [PATCH trivial 00/21] spelling fixes for 8.2 Michael Tokarev
2023-11-14 16:58 ` [PATCH trivial 01/21] bsd-user: spelling fixes: necesary, agrument, undocummented Michael Tokarev
2023-11-14 17:34   ` Warner Losh
2023-11-14 16:58 ` [PATCH trivial 02/21] linux-user: spelling fixes: othe, necesary Michael Tokarev
2023-11-15  7:10   ` Thomas Huth
2023-11-14 16:58 ` [PATCH trivial 03/21] hw/cxl: spelling fixes: limitaions, potentialy, intialized Michael Tokarev
2023-11-15  7:10   ` Thomas Huth
2023-11-14 16:58 ` [PATCH trivial 04/21] gdbstub: spelling fix: respectivelly Michael Tokarev
2023-11-15  7:11   ` Thomas Huth
2023-11-14 16:58 ` [PATCH trivial 05/21] docs/about/deprecated.rst: spelling fix: becase Michael Tokarev
2023-11-14 19:04   ` Thomas Huth
2023-11-16 14:25   ` Juan Quintela
2023-11-14 16:58 ` [PATCH trivial 06/21] docs/devel/migration.rst: spelling fix: doen't Michael Tokarev
2023-11-14 19:05   ` Thomas Huth
2023-11-15  6:41     ` Michael Tokarev
2023-11-15  6:46       ` Thomas Huth
2023-11-15  8:59         ` Michael Tokarev
2023-11-16 14:27       ` Juan Quintela [this message]
2023-11-14 16:58 ` [PATCH trivial 07/21] docs/system/arm/emulation.rst: spelling fix: Enhacements Michael Tokarev
2023-11-14 19:06   ` Thomas Huth
2023-11-14 16:58 ` [PATCH trivial 08/21] target/arm/tcg: spelling fixes: alse, addreses Michael Tokarev
2023-11-14 20:19   ` Richard Henderson
2023-11-14 16:58 ` [PATCH trivial 09/21] target/hppa: spelling fixes: Indicies, Truely Michael Tokarev
2023-11-14 20:20   ` Richard Henderson
2023-11-14 16:58 ` [PATCH trivial 10/21] migration/rdma.c: spelling fix: asume Michael Tokarev
2023-11-15  7:12   ` Thomas Huth
2023-11-14 16:58 ` [PATCH trivial 11/21] contrib/vhost-user-gpu/virgl.c: spelling fix: mesage Michael Tokarev
2023-11-15  6:18   ` Marc-André Lureau
2023-11-14 16:58 ` [PATCH trivial 12/21] hw/mem/memory-device.c: spelling fix: ontaining Michael Tokarev
2023-11-15  7:12   ` Thomas Huth
2023-11-14 16:58 ` [PATCH trivial 13/21] hw/net/cadence_gem.c: spelling fixes: Octects Michael Tokarev
2023-11-15  7:13   ` Thomas Huth
2023-11-15  8:40   ` Luc Michel
2023-11-14 16:58 ` [PATCH trivial 14/21] include/block/ufs.h: spelling fix: setted Michael Tokarev
2023-11-14 23:49   ` Jeuk Kim
2023-11-15  7:13   ` Thomas Huth
2023-11-14 16:58 ` [PATCH trivial 15/21] include/hw/hyperv/dynmem-proto.h: spelling fix: nunber Michael Tokarev
2023-11-14 22:29   ` Maciej S. Szmigiero
2023-11-14 16:58 ` [PATCH trivial 16/21] include/hw/virtio/vhost.h: spelling fix: sate Michael Tokarev
2023-11-15  7:14   ` Thomas Huth
2023-11-14 16:58 ` [PATCH trivial 17/21] target/riscv/cpu.h: spelling fix: separatly Michael Tokarev
2023-11-15  7:15   ` Thomas Huth
2023-11-21  3:29   ` Alistair Francis
2023-11-14 16:58 ` [PATCH trivial 18/21] tests/qtest/migration-test.c: spelling fix: bandwith Michael Tokarev
2023-11-14 19:07   ` Thomas Huth
2023-11-14 16:58 ` [PATCH trivial 19/21] tests/qtest/ufs-test.c: spelling fix: tranfer Michael Tokarev
2023-11-14 19:07   ` Thomas Huth
2023-11-14 23:51   ` Jeuk Kim
2023-11-14 16:58 ` [PATCH trivial 20/21] util/filemonitor-inotify.c: spelling fix: kenel Michael Tokarev
2023-11-14 20:30   ` Vladimir Sementsov-Ogievskiy
2023-11-14 16:58 ` [PATCH trivial 21/21] util/range.c: spelling fix: inbetween Michael Tokarev
2023-11-14 17:13   ` Eric Auger
2023-11-14 17:34   ` Cédric Le Goater

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=87a5rdrcwy.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@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 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.