From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Mark McLoughlin <markmc@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Mike Frysinger <vapier@gentoo.org>
Subject: [PULL] virtio
Date: Fri, 12 Jun 2009 22:18:34 +0930 [thread overview]
Message-ID: <200906122218.34829.rusty@rustcorp.com.au> (raw)
The following changes since commit 8ebf975608aaebd7feb33d77f07ba21a6380e086:
Randy Dunlap (1):
block: fix kernel-doc in recent block/ changes
are available in the git repository at:
ssh://master.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-virtio.git master
Christian Borntraeger (2):
virtio: fix id_matching for virtio drivers
virtio: enhance id_matching for virtio drivers
Mark McLoughlin (2):
virtio: teach virtio_has_feature() about transport features
virtio: indirect ring entries (VIRTIO_RING_F_INDIRECT_DESC)
Michael S. Tsirkin (3):
virtio: find_vqs/del_vqs virtio operations
virtio_pci: split up vp_interrupt
virtio_pci: optional MSI-X support
Mike Frysinger (1):
virtio_blk: add missing __dev{init,exit} markings
Rusty Russell (5):
virtio: fix obsolete documentation on probe function
virtio: meet virtio spec by finalizing features before using device
virtio: add names to virtqueue struct, mapping from devices to queues.
virtio: expose features in sysfs
virtio: handle short buffers in virtio_rng.
drivers/block/virtio_blk.c | 10 +-
drivers/char/hw_random/virtio-rng.c | 30 +++--
drivers/char/virtio_console.c | 26 ++--
drivers/lguest/lguest_device.c | 41 +++++-
drivers/net/virtio_net.c | 45 ++---
drivers/s390/kvm/kvm_virtio.c | 43 +++++-
drivers/virtio/virtio.c | 29 +++-
drivers/virtio/virtio_balloon.c | 27 ++--
drivers/virtio/virtio_pci.c | 307 ++++++++++++++++++++++++++++++-----
drivers/virtio/virtio_ring.c | 102 +++++++++++-
include/linux/virtio.h | 15 +-
include/linux/virtio_config.h | 49 +++++--
include/linux/virtio_pci.h | 10 +-
include/linux/virtio_ring.h | 8 +-
net/9p/trans_virtio.c | 6 +-
scripts/mod/file2alias.c | 2 +-
16 files changed, 592 insertions(+), 158 deletions(-)
next reply other threads:[~2009-06-12 12:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 12:48 Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-28 18:43 [PULL] virtio Michael S. Tsirkin
2010-03-07 10:42 Michael S. Tsirkin
[not found] ` <40B76F19-1E35-4956-A34E-0A83A403F97D@suse.de>
2010-03-07 11:04 ` Michael S. Tsirkin
2010-03-07 11:11 ` Alexander Graf
2010-03-22 14:34 Michael S. Tsirkin
2010-05-19 12:53 Rusty Russell
2010-08-05 3:37 Rusty Russell
[not found] <87wrbkvh3v.fsf@rustcorp.com.au>
2011-11-01 11:45 ` Michael S. Tsirkin
2011-11-01 12:33 ` Sasha Levin
2011-11-01 12:42 ` Michael S. Tsirkin
2011-11-01 12:45 ` Sasha Levin
2011-11-02 1:09 ` Rusty Russell
2011-11-02 4:52 ` Sasha Levin
2011-11-02 22:07 ` Rusty Russell
2012-05-22 2:51 Rusty Russell
2012-05-22 3:24 ` Linus Torvalds
2012-05-22 4:29 ` Rusty Russell
2012-10-05 1:39 Rusty Russell
2013-02-26 5:33 Rusty Russell
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=200906122218.34829.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mst@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=vapier@gentoo.org \
--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 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).