From: Paolo Bonzini <pbonzini@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: QEMU <qemu-devel@nongnu.org>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] serial: Fix double migration data
Date: Tue, 31 Mar 2020 17:23:45 +0200 [thread overview]
Message-ID: <6b30270b-207f-4b5d-bc4c-323827868f60@redhat.com> (raw)
In-Reply-To: <CAJ+F1CJzdso1xNj+XyiriByHzYekz74+JRCCQ4a6ygWLrCGMvA@mail.gmail.com>
On 30/03/20 19:56, Marc-André Lureau wrote:
>>> Why do you make it a sub-state?
>> Because it's consistent with serial-isa and it's simple.
> ok, lgtm then
>
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-03-31 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 16:47 [PATCH] serial: Fix double migration data Dr. David Alan Gilbert (git)
2020-03-30 17:29 ` Marc-André Lureau
2020-03-30 17:41 ` Dr. David Alan Gilbert
2020-03-30 17:56 ` Marc-André Lureau
2020-03-31 15:23 ` Paolo Bonzini [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=6b30270b-207f-4b5d-bc4c-323827868f60@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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).