From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: [Qemu-devel] [PULL] virtio, pci fixes
Date: Thu, 13 May 2010 01:37:26 +0300 [thread overview]
Message-ID: <20100512223726.GA26068@redhat.com> (raw)
The following changes since commit 54d7cf136f040713095cbc064f62d753bff6f9d2:
doc: Clean up monitor command function index (2010-05-10 11:36:04 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git for_anthony
Alex Williamson (1):
pci: cleanly backout of pci_qdev_init()
Michael S. Tsirkin (3):
pci: irq_state vmstate breakage
virtio: invoke set_features on load
virtio-net: return with value in void function
hw/pci.c | 20 +++++++++++++-------
hw/virtio-net.c | 2 +-
hw/virtio.c | 2 ++
3 files changed, 16 insertions(+), 8 deletions(-)
next reply other threads:[~2010-05-13 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 22:37 Michael S. Tsirkin [this message]
2010-05-17 17:52 ` [Qemu-devel] [PULL] virtio, pci fixes Anthony Liguori
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=20100512223726.GA26068@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--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).