From: Michael Tokarev <mjt@tls.msk.ru>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Serge Hallyn" <serge.hallyn@canonical.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
"Alexander Graf" <agraf@suse.de>,
"Anthony Liguori" <aliguori@amazon.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] Should we have a 2.0-rc3 ?
Date: Sat, 12 Apr 2014 12:48:41 +0400 [thread overview]
Message-ID: <5348FDE9.10807@msgid.tls.msk.ru> (raw)
In-Reply-To: <CAFEAcA8LcRuB82HHO1e-6eJu-=u4yZxT4UdrOhwzgx0J+ZVxUQ@mail.gmail.com>
11.04.2014 21:37, Peter Maydell wrote:
[]
> Patches on list but need review/ack and/or not sure whether to apply:
> * kvm_physical_sync_dirty_bitmap bug
Paolo proposed to revert the change which lead to that bug, but it
seems wrong thing to do, since original code was clearly wrong.
Maybe it is a good idea to apply Hallyn's version instead of mine
(when done against the right tree), as it makes the code closer
to the original version but more correct.
> * vmxnet3 patches
I think this is not dangerous to go in before 2.0. We wont have more
testing even if it were applied much earlier, because this device is
rather exotic in qemu world and isn't used often. On the other hand,
having less CVE IDs for a release is good, in my opinion.
> Raised as issues but no patches:
> * PCI bus naming
> * win64 virtio-scsi regression
>
> Assistance welcomed in moving patches in the last two
> categories into either "ready to apply" or "not for 2.0" :-)
>
> thanks
> -- PMM
>
prev parent reply other threads:[~2014-04-12 8:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 11:17 [Qemu-devel] Should we have a 2.0-rc3 ? Peter Maydell
2014-04-10 11:24 ` Alexander Graf
2014-04-10 15:22 ` Michael S. Tsirkin
2014-04-10 11:49 ` Kevin Wolf
2014-04-10 12:44 ` Eric Blake
2014-04-10 12:46 ` Alexander Graf
2014-04-10 12:51 ` Eric Blake
2014-04-10 12:56 ` Alexander Graf
2014-04-10 13:41 ` Ján Tomko
2014-04-10 13:45 ` Alexander Graf
2014-04-10 15:02 ` Eric Blake
2014-04-10 15:27 ` Alexander Graf
2014-04-10 15:38 ` Eric Blake
2014-04-10 15:42 ` Alexander Graf
2014-04-11 8:01 ` Markus Armbruster
2014-04-11 8:37 ` Daniel P. Berrange
2014-04-10 15:26 ` Michael S. Tsirkin
2014-04-10 18:55 ` Cole Robinson
2014-04-10 21:30 ` Peter Maydell
2014-04-11 17:37 ` Peter Maydell
2014-04-11 22:55 ` Alexander Graf
2014-04-12 1:49 ` Paolo Bonzini
2014-04-12 8:48 ` Michael Tokarev [this message]
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=5348FDE9.10807@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=serge.hallyn@canonical.com \
/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.