All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "lkml" <linux-kernel@vger.kernel.org>
Cc: Amit Shah <amit.shah@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Huth <thuth@linux.vnet.ibm.com>
Subject: [PULL] virtio-next fixes
Date: Tue, 17 Mar 2015 12:19:54 +1030	[thread overview]
Message-ID: <877fugmlz1.fsf@rustcorp.com.au> (raw)

The following changes since commit 6587457b4b3d663b237a0f95ddf6e67d1828c8ea:

  Merge tag 'dma-buf-for-4.0-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/sumits/dma-buf (2015-03-04 09:59:51 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git tags/virtio-next-for-linus

for you to fetch changes up to 704a0b5f234db26de5203740999e39523cfa4e3a:

  virtio_mmio: fix access width for mmio (2015-03-17 12:12:21 +1030)

----------------------------------------------------------------
Not entirely surprising: the ongoing QEMU work on virtio 1.0 has revealed
more minor issues with our virtio 1.0 drivers just introduced in the
kernel.

(I would normally use my fixes branch for this, but there were a batch of them...)

Thanks,
Rusty.

----------------------------------------------------------------
Michael S. Tsirkin (11):
      virtio_console: init work unconditionally
      virtio_console: avoid config access from irq
      virtio_balloon: set DRIVER_OK before using device
      virtio_blk: typo fix
      virtio_blk: fix comment for virtio 1.0
      virtio-balloon: do not call blocking ops when !TASK_RUNNING
      9p/trans_virtio: fix hot-unplug
      virtio_rpmsg: set DRIVER_OK before using device
      virtio_mmio: generation support
      uapi/virtio_scsi: allow overriding CDB/SENSE size
      virtio_mmio: fix access width for mmio

 drivers/char/virtio_console.c    | 19 ++++++++-
 drivers/rpmsg/virtio_rpmsg_bus.c | 17 +++++++-
 drivers/virtio/virtio_balloon.c  | 21 +++++++---
 drivers/virtio/virtio_mmio.c     | 90 ++++++++++++++++++++++++++++++++++++----
 include/uapi/linux/virtio_blk.h  |  8 +++-
 include/uapi/linux/virtio_scsi.h | 12 +++++-
 net/9p/trans_virtio.c            | 24 +++++++++--
 7 files changed, 168 insertions(+), 23 deletions(-)

                 reply	other threads:[~2015-03-17  1:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=877fugmlz1.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@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.