From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, pbonzini@redhat.com, dgilbert@redhat.com,
quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: catch unknown flag combinations in ram_load
Date: Tue, 24 Jun 2014 09:49:24 -0600 [thread overview]
Message-ID: <53A99E04.4090302@redhat.com> (raw)
In-Reply-To: <1403602356-13687-1-git-send-email-pl@kamp.de>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
On 06/24/2014 03:32 AM, Peter Lieven wrote:
> this patch extends commit db80fac by not only checking
> for unknown flags, but also filtering out unknown flag
> combinations.
>
> Suggested-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> arch_init.c | 62 ++++++++++++++++++++++++++++++-----------------------------
> 1 file changed, 32 insertions(+), 30 deletions(-)
>
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-06-24 15:49 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 [this message]
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
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=53A99E04.4090302@redhat.com \
--to=eblake@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--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).