Am 20.05.2013 14:25, schrieb Anthony Liguori: > Paolo Bonzini <pbonz...@redhat.com> writes: > >> Il 20/05/2013 13:28, Stefan Weil ha scritto: >>> Am 20.05.2013 13:00, schrieb Paolo Bonzini: >>>> 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-ema...@freebsd.org> >>>> [PATCH v2] Rename hexdump to avoid FreeBSD libutil conflict >>>> >>>> <1369046780-17498-1-git-send-email-pbonz...@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-hpous...@reactos.org> >>>> [PATCH for-1.5] osdep: fix qemu_anon_ram_free trace (+ fix compilation >>>> on 32 bit hosts) >>> See also http://patchwork.ozlabs.org/patch/244757/ >> Yes, they are identical. >> >>>> <1369032665-18159-2-git-send-email-li...@linux.vnet.ibm.com> >>>> [PATCH 1/3] chardev: Make consistent with udp device for new qapi backend >>>> (not the rest of the series) >>>> >>>> There is also <20130520081814.ga8...@redhat.com>, but I think it's >>>> too intrusive. >>> Plus this one, please: >>> >>> http://patchwork.ozlabs.org/patch/244758/ >>> spitz: Fix compiler warning (MinGW-w64) >> Agreed. > We don't build with -Werror on MinGW-w64 so a warning fix is very low > priority. It needs to wait for stable. > > Regards, > > Anthony Liguori
I don't mind waiting. For your information: MinGW-w64 normally should compile without warnings when a recent set of MinGW-w64 include files is used. Please don't forget http://patchwork.ozlabs.org/patch/244757/ _before_ Paolo's list. Thanks, Stefan Weil
