From: Peter Lieven <pl@kamp.de>
To: Peter Maydell <peter.maydell@linaro.org>,
Amit Shah <amit.shah@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] migration: catch unknown flag combinations in ram_load
Date: Wed, 09 Jul 2014 15:23:51 +0200 [thread overview]
Message-ID: <53BD4267.2030303@kamp.de> (raw)
In-Reply-To: <CAFEAcA_fswzzvecPw4n_2b45jwUNoay6_j3arMEJWGRmm9+xvg@mail.gmail.com>
Am 09.07.2014 13:00, schrieb Peter Maydell:
> On 9 July 2014 11:56, Amit Shah <amit.shah@redhat.com> wrote:
>> On (Wed) 09 Jul 2014 [11:50:18], Peter Maydell wrote:
>>> OK; we're treating those as bugs so yes, I think this is 2.1
>>> material. Has somebody other than the original author tested
>>> it? (That's a step that would usually be done by Juan as the
>>> maintainer.) If somebody can provide a Tested-by: I'm happy
>>> to apply it to master.
>> Not really sure if Juan did that as part of his 'thanks, applied'
>> workflow, but I'll run this through the autotest migration tests and
>> report back.
> Thanks; it seems better to double-check given where we are in
> the release cycle.
We have also an:
Reviewed-by: Eric Blake <eblake@redhat.com>
Maybe he tested as well.
If there are any doubts we should postpone this for 2.2. The preceding
patch is in 2.1 and should catch already a lot of cases.
Peter
next prev parent reply other threads:[~2014-07-09 13:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 9:32 [Qemu-devel] [PATCH] migration: catch unknown flag combinations in ram_load Peter Lieven
2014-06-24 15:49 ` Eric Blake
2014-06-25 11:55 ` Juan Quintela
2014-07-08 20:55 ` Peter Lieven
2014-07-09 4:25 ` Amit Shah
2014-07-09 10:28 ` Peter Maydell
2014-07-09 10:44 ` Amit Shah
2014-07-09 10:50 ` Peter Maydell
2014-07-09 10:56 ` Amit Shah
2014-07-09 11:00 ` Peter Maydell
2014-07-09 13:23 ` Peter Lieven [this message]
2014-07-09 13:55 ` Eric Blake
2014-07-11 12:52 ` Amit Shah
2014-08-21 21:57 ` Peter Lieven
2014-08-22 3:57 ` Amit Shah
2014-09-02 9:17 ` Peter Lieven
2014-09-23 9:46 ` Paolo Bonzini
2014-09-23 9:51 ` Paolo Bonzini
2014-09-30 6:38 ` Peter Lieven
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=53BD4267.2030303@kamp.de \
--to=pl@kamp.de \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).