From: Anthony Liguori <aliguori@us.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>, Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] pending 1.5 patches
Date: Mon, 20 May 2013 07:25:53 -0500 [thread overview]
Message-ID: <87zjvp25ym.fsf@codemonkey.ws> (raw)
In-Reply-To: <519A09AE.5080205@redhat.com>
Paolo Bonzini <pbonzini@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-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)
>>
>> See also http://patchwork.ozlabs.org/patch/244757/
>
> Yes, they are identical.
>
>>> <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)
>>>
>>> There is also <20130520081814.GA8162@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
>
> Paolo
next prev parent reply other threads:[~2013-05-20 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 11:00 [Qemu-devel] pending 1.5 patches Paolo Bonzini
2013-05-20 11:28 ` Stefan Weil
2013-05-20 11:31 ` Paolo Bonzini
2013-05-20 12:25 ` Anthony Liguori [this message]
2013-05-20 15:04 ` Stefan Weil
2013-05-20 12:24 ` Anthony Liguori
2013-05-20 12:28 ` Michael S. Tsirkin
2013-05-20 15:07 ` Eric Blake
2013-05-20 15:16 ` Paolo Bonzini
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=87zjvp25ym.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).