From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60797) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UeRpG-0007VY-4b for qemu-devel@nongnu.org; Mon, 20 May 2013 11:16:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UeRpE-0005RA-9r for qemu-devel@nongnu.org; Mon, 20 May 2013 11:16:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:9332) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UeRpE-0005R2-0t for qemu-devel@nongnu.org; Mon, 20 May 2013 11:16:36 -0400 Message-ID: <519A3E4D.7030208@redhat.com> Date: Mon, 20 May 2013 17:16:29 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <519A0268.7050308@redhat.com> <519A3C25.1070108@redhat.com> In-Reply-To: <519A3C25.1070108@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] pending 1.5 patches List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: Anthony Liguori , qemu-devel -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 20/05/2013 17:07, Eric Blake ha scritto: > On 05/20/2013 05:00 AM, Paolo Bonzini wrote: >> I see the following patches on the list that IMO deserve >> inclusion into 1.5. All of them should be low-risk. >> >> <1368718348-15199-1-git-send-email-emaste@freebsd.org> [PATCH v2] >> Rename hexdump to avoid FreeBSD libutil conflict >> >> <1369046780-17498-1-git-send-email-pbonzini@redhat.com> [PATCH >> for-1.5 resend] vl: new runstate transition: >> RUN_STATE_GUEST_PANICKED -> RUN_STATE_FINISH_MIGRATE >> >> <1369045989-14016-1-git-send-email-hpoussin@reactos.org> [PATCH >> for-1.5] osdep: fix qemu_anon_ram_free trace (+ fix compilation >> on 32 bit hosts) >> >> <1369032665-18159-2-git-send-email-lilei@linux.vnet.ibm.com> >> [PATCH 1/3] chardev: Make consistent with udp device for new qapi >> backend (not the rest of the series) > > Actually, I argue that patch 2/3 of that series would also be an > ABI change if it is not included NOW, since it renames a union > member that to date has not been released. As written, patch 2/3 is an ABI change compared to 1.4, so it cannot go in anyway, at least not in this shape. Paolo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRmj5NAAoJEBvWZb6bTYbykzMQAJzBl1g27TW/vyei9e0SI7Ap V2h/A+eCBiPaxJQisem6DA7YOlQLdTEgZXMRrYgqwR6r5tKTYd3lokW5jCmXTZ6Q dD6cfw7Z4QTRl0FLmVey0rzna4iCf89xyBAB68Xt8ZnZGxc0DiR/82pjZCZESZ9k bTDheIjdW7jJEdEUFx7/gDWTfun4rwvD6j/bTXfBKB6DNQ5s559wc2aiVRyZhBcZ v2abMCK2atKmyjST61GOEUKniQtRzMmvMoorBcvytPv03sY9KFc6awINTZ3VlhhI g1ht3XepSYD41Z1cnQL0vZe7ILw8eZtVLsRwaV6u0rlp6dcq8s6MoLtwTUp8Lfcc b0+bzk30eND16x1IsMKQ2LKyCC5dRVnVNtNrmDnoDMpjkDjbI3TFmZcH3icseEc7 h/OmxxWpsfEghwCQe0fnch8ruV69Ba0FFxnBt5DWYKuv6aEuEAmKHtxFakrlT41P lSz++AetLSy2tm7ssn+L3eb6a7EMhf+L0i62KvzK8Eewhqkl7krGzAmjhXwItk2r VK2v+KtCUMFB3D3Y4FXp3RKsLsFvx8xaprsE+5sDfrmKFqCVL6sMbSfckdfOEuhg sstB9AzB6u/+N3mLh49172vhq63sSEcW1It1HuCJIlvvOtZY1mimATo6lsrZGz0K +oOBg8Fol5itqXtbdPuE =aOgl -----END PGP SIGNATURE-----