From: Stefan Weil <sw@weilnetz.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] pending 1.5 patches
Date: Mon, 20 May 2013 13:28:50 +0200 [thread overview]
Message-ID: <519A08F2.1020007@weilnetz.de> (raw)
In-Reply-To: <519A0268.7050308@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
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/
> <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.
>
> Paolo
Plus this one, please:
http://patchwork.ozlabs.org/patch/244758/
spitz: Fix compiler warning (MinGW-w64)
Stefan
[-- Attachment #2: Type: text/html, Size: 2464 bytes --]
next prev parent reply other threads:[~2013-05-20 11:29 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 [this message]
2013-05-20 11:31 ` Paolo Bonzini
2013-05-20 12:25 ` Anthony Liguori
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=519A08F2.1020007@weilnetz.de \
--to=sw@weilnetz.de \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.