From: Peter Xu <peterx@redhat.com>
To: marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
qemu-block@nongnu.org, Jason Wang <jasowang@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Leonardo Bras <leobras@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
John Snow <jsnow@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 0/5] RFC: migration: check required entries and sections are loaded
Date: Wed, 4 Oct 2023 12:26:06 -0400 [thread overview]
Message-ID: <ZR2SHnvPGR4xKKQ2@x1n> (raw)
In-Reply-To: <20230926155925.1396309-1-marcandre.lureau@redhat.com>
On Tue, Sep 26, 2023 at 07:59:20PM +0400, marcandre.lureau@redhat.com wrote:
> Marc-André Lureau (5):
> block/fdc: 'phase' is not needed on load
> virtio: make endian_needed() work during loading
> net/slirp: use different IDs for each instance
First 3 patches are bug fixes, am I right?
It'll be great if they can be acked (or even picked up earlier?) by
subsystem maintainers if so, and copy stable if justified proper.
Thanks,
--
Peter Xu
prev parent reply other threads:[~2023-10-04 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 15:59 [PATCH 0/5] RFC: migration: check required entries and sections are loaded marcandre.lureau
2023-09-26 15:59 ` [PATCH 1/5] block/fdc: 'phase' is not needed on load marcandre.lureau
2023-09-26 15:59 ` [PATCH 2/5] virtio: make endian_needed() work during loading marcandre.lureau
2023-09-26 15:59 ` [PATCH 3/5] net/slirp: use different IDs for each instance marcandre.lureau
2023-09-26 15:59 ` [PATCH 4/5] RFC: migration: check required subsections are loaded, once marcandre.lureau
2023-10-04 16:16 ` Peter Xu
2023-09-26 15:59 ` [PATCH 5/5] RFC: migration: check required entries " marcandre.lureau
2023-10-04 16:26 ` Peter Xu [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=ZR2SHnvPGR4xKKQ2@x1n \
--to=peterx@redhat.com \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=leobras@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=samuel.thibault@ens-lyon.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).