From: Pawel Moll <pawel.moll@arm.com>
To: Rusty Russell <rusty@rustcorp.com.au>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: virtio fixes pull for 4.0?
Date: Mon, 23 Mar 2015 09:29:51 +0000 [thread overview]
Message-ID: <1427102991.3726.0.camel__32388.1062133752$1427103013$gmane$org@arm.com> (raw)
In-Reply-To: <87y4n6wsmo.fsf@rustcorp.com.au>
On Mon, 2015-03-09 at 07:13 +0000, Rusty Russell wrote:
> > virtio_mmio: generation support
> > virtio_mmio: fix endian-ness for mmio these two are waiting for ack by Pawel
> >
> > These two fix bugs in virtio 1.0 code for mmio.
> > Host code for that was AFAIK not posted, so I can't test properly.
> > Pawel?
>
> I'm waiting on Acks for these two.
Right, sorry about being silent for a while - I forked and was on
paternity leave...
Will go through the thread and respond today.
Pawel
next prev parent reply other threads:[~2015-03-23 9:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 19:30 virtio fixes pull for 4.0? Michael S. Tsirkin
2015-03-07 19:30 ` [Qemu-devel] " Michael S. Tsirkin
2015-03-09 7:13 ` Rusty Russell
2015-03-09 7:13 ` [Qemu-devel] " Rusty Russell
2015-03-09 8:50 ` Cornelia Huck
2015-03-09 8:50 ` [Qemu-devel] " Cornelia Huck
2015-03-16 5:06 ` Michael S. Tsirkin
2015-03-16 5:06 ` [Qemu-devel] " Michael S. Tsirkin
2015-03-17 1:50 ` Rusty Russell
2015-03-17 1:50 ` Rusty Russell
2015-03-17 1:50 ` [Qemu-devel] " Rusty Russell
2015-03-23 9:29 ` Pawel Moll [this message]
2015-03-23 9:29 ` Pawel Moll
2015-03-23 9:29 ` [Qemu-devel] " Pawel Moll
2015-03-07 19:30 Michael S. Tsirkin
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='1427102991.3726.0.camel__32388.1062133752$1427103013$gmane$org@arm.com' \
--to=pawel.moll@arm.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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.