From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56042) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X4rqx-00057p-2z for qemu-devel@nongnu.org; Wed, 09 Jul 2014 09:24:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X4rqn-00026W-3s for qemu-devel@nongnu.org; Wed, 09 Jul 2014 09:24:06 -0400 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:36495 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X4rqm-00025z-P2 for qemu-devel@nongnu.org; Wed, 09 Jul 2014 09:23:57 -0400 Message-ID: <53BD4267.2030303@kamp.de> Date: Wed, 09 Jul 2014 15:23:51 +0200 From: Peter Lieven MIME-Version: 1.0 References: <1403602356-13687-1-git-send-email-pl@kamp.de> <874mz919w5.fsf@troll.troll> <20140709042557.GA10283@grmbl.mre> <20140709104457.GE27615@grmbl.mre> <20140709105620.GG27615@grmbl.mre> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] migration: catch unknown flag combinations in ram_load List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Amit Shah Cc: Paolo Bonzini , QEMU Developers , "Dr. David Alan Gilbert" , Juan Quintela Am 09.07.2014 13:00, schrieb Peter Maydell: > On 9 July 2014 11:56, Amit Shah 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 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