From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] virtio-1 related entry in 2.4 Changelog, please
Date: Thu, 3 Sep 2015 22:53:03 +0300 [thread overview]
Message-ID: <20150903225251-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <CAFEAcA9ui769wCXXMCcH78SbeE-_FeizD_+qjaV8SHZRS0x7sA@mail.gmail.com>
On Thu, Sep 03, 2015 at 06:47:55PM +0100, Peter Maydell wrote:
> Our changelog for QEMU 2.4 (http://wiki.qemu.org/ChangeLog/2.4)
> currently has a line in it saying
> " * FIXME: virtio 1"
>
> Could somebody familiar with the level of our virtio-1 support
> in 2.4 please fix this, before everybody forgets exactly what
> 2.4 did and didn't support?
>
> thanks
> -- PMM
I'll send a summary Sunday.
next prev parent reply other threads:[~2015-09-03 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 17:47 [Qemu-devel] virtio-1 related entry in 2.4 Changelog, please Peter Maydell
2015-09-03 19:53 ` Michael S. Tsirkin [this message]
2015-09-07 7:30 ` Michael S. Tsirkin
2015-09-07 9:18 ` Peter Maydell
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=20150903225251-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).