From: Fabiano Rosas <farosas@suse.de>
To: Fiona Ebner <f.ebner@proxmox.com>, qemu-devel@nongnu.org
Cc: "Peter Xu" <peterx@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
qemu-stable@nongnu.org
Subject: Re: [PULL 6/9] virtio-gpu: fix v2 migration
Date: Wed, 29 May 2024 10:26:40 -0300 [thread overview]
Message-ID: <8734q0g35b.fsf@suse.de> (raw)
In-Reply-To: <94b38346-7ad7-4fa4-b7e8-3ba00cc72f16@proxmox.com>
Fiona Ebner <f.ebner@proxmox.com> writes:
> CC-ing stable, because this already is an issue in 9.0.0
>
Thank you for pointing this out. I was expecting b4 to find the tag, but
I just now noticed that the CC was added by Peter as a reply to the
message and not originally via the patch headers, so I should have added
it manually.
next prev parent reply other threads:[~2024-05-29 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 22:20 [PULL 0/9] Migration patches for 2024-05-22 Fabiano Rosas
2024-05-22 22:20 ` [PULL 1/9] migration/colo: Minor fix for colo error message Fabiano Rosas
2024-05-22 22:20 ` [PULL 2/9] migration/colo: make colo_incoming_co() return void Fabiano Rosas
2024-05-22 22:20 ` [PULL 3/9] migration/colo: Tidy up bql_unlock() around bdrv_activate_all() Fabiano Rosas
2024-05-22 22:20 ` [PULL 4/9] migration: add "exists" info to load-state-field trace Fabiano Rosas
2024-05-22 22:20 ` [PULL 5/9] migration: fix a typo Fabiano Rosas
2024-05-22 22:20 ` [PULL 6/9] virtio-gpu: fix v2 migration Fabiano Rosas
2024-05-29 10:50 ` Fiona Ebner
2024-05-29 13:26 ` Fabiano Rosas [this message]
2024-05-22 22:20 ` [PULL 7/9] hw/core/machine: move compatibility flags for VirtIO-net USO to machine 8.1 Fabiano Rosas
2024-05-22 22:20 ` [PULL 8/9] tests/qtest/migration-test: Run some basic tests on s390x and ppc64 with TCG, too Fabiano Rosas
2024-05-22 22:20 ` [PULL 9/9] tests/qtest/migration-test: Fix the check for a successful run of analyze-migration.py Fabiano Rosas
2024-05-23 2:02 ` [PULL 0/9] Migration patches for 2024-05-22 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=8734q0g35b.fsf@suse.de \
--to=farosas@suse.de \
--cc=f.ebner@proxmox.com \
--cc=marcandre.lureau@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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).