From: Olaf Hering <olaf@aepfle.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Juergen Gross" <jgross@suse.com>,
"Ian Jackson" <iwj@xenproject.org>, "Wei Liu" <wl@xen.org>
Subject: Re: [PATCH 0/5] tools/migration: Py3 fixes, and page type helpers
Date: Tue, 6 Jul 2021 09:11:29 +0200 [thread overview]
Message-ID: <20210706091129.45451433.olaf@aepfle.de> (raw)
In-Reply-To: <20210705191027.15107-1-andrew.cooper3@citrix.com>
Am Mon, 5 Jul 2021 20:10:22 +0100
schrieb Andrew Cooper <andrew.cooper3@citrix.com>:
> tools/python: handle libxl__physmap_info.name properly in convert-legacy-stream
> tools/python: fix Python3.4 TypeError in format string
> tools/migration: unify known page type checking
> tools/migration: unify type checking for data pfns in the VM
> tools/migration: unify type checking for data pfns in migration stream
Tested-by: Olaf Hering <olaf@aepfle.de>
Olaf
prev parent reply other threads:[~2021-07-06 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 19:10 [PATCH 0/5] tools/migration: Py3 fixes, and page type helpers Andrew Cooper
2021-07-05 19:10 ` [PATCH 1/5] tools/python: handle libxl__physmap_info.name properly in convert-legacy-stream Andrew Cooper
2021-07-05 19:49 ` Marek Marczykowski-Górecki
2021-07-05 19:10 ` [PATCH 2/5] tools/python: fix Python3.4 TypeError in format string Andrew Cooper
2021-07-05 19:51 ` Marek Marczykowski-Górecki
2021-07-05 19:10 ` [PATCH 3/5] tools/migration: unify known page type checking Andrew Cooper
2021-07-05 19:10 ` [PATCH 4/5] tools/migration: unify type checking for data pfns in the VM Andrew Cooper
2021-07-05 19:10 ` [PATCH 5/5] tools/migration: unify type checking for data pfns in migration stream Andrew Cooper
2021-07-06 4:57 ` Juergen Gross
2021-07-06 7:11 ` Olaf Hering [this message]
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=20210706091129.45451433.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew.cooper3@citrix.com \
--cc=iwj@xenproject.org \
--cc=jgross@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.