From: Fabiano Rosas <farosas@suse.de>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
peterx@redhat.com
Cc: eblake@redhat.com, armbru@redhat.com, pbonzini@redhat.com,
qemu-devel@nongnu.org, vsementsov@yandex-team.ru,
yc-core@yandex-team.ru
Subject: Re: [PATCH v3 1/4] migration: move trace-point from migrate_fd_error to migrate_set_error
Date: Thu, 25 Apr 2024 17:03:23 -0300 [thread overview]
Message-ID: <871q6ti510.fsf@suse.de> (raw)
In-Reply-To: <20240425181551.1465739-2-vsementsov@yandex-team.ru>
Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> writes:
> Cover more cases by trace-point.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
next prev parent reply other threads:[~2024-04-25 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 18:15 [PATCH v3 0/4] migration: do not exit on incoming failure Vladimir Sementsov-Ogievskiy
2024-04-25 18:15 ` [PATCH v3 1/4] migration: move trace-point from migrate_fd_error to migrate_set_error Vladimir Sementsov-Ogievskiy
2024-04-25 20:03 ` Fabiano Rosas [this message]
2024-04-25 18:15 ` [PATCH v3 2/4] migration: process_incoming_migration_co(): complete cleanup on failure Vladimir Sementsov-Ogievskiy
2024-04-25 20:03 ` Fabiano Rosas
2024-04-25 18:15 ` [PATCH v3 3/4] migration: process_incoming_migration_co(): rework error reporting Vladimir Sementsov-Ogievskiy
2024-04-25 20:21 ` Fabiano Rosas
2024-04-25 18:15 ` [PATCH v3 4/4] qapi: introduce exit-on-error parameter for migrate-incoming Vladimir Sementsov-Ogievskiy
2024-04-25 20:30 ` Fabiano Rosas
2024-04-29 7:45 ` Vladimir Sementsov-Ogievskiy
2024-04-29 13:06 ` Fabiano Rosas
2024-04-29 15:03 ` Vladimir Sementsov-Ogievskiy
2024-04-26 5:17 ` Markus Armbruster
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=871q6ti510.fsf@suse.de \
--to=farosas@suse.de \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
--cc=yc-core@yandex-team.ru \
/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).