All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Cc: mst@redhat.com, jan.kiszka@siemens.com, fernando@oss.ntt.co.jp,
	kakuta.hayato@oss.ntt.co.jp, jbaron@redhat.com
Subject: [Qemu-devel] [PULL] rtl8139,pci,msi
Date: Thu, 7 Jun 2012 19:38:30 +0300	[thread overview]
Message-ID: <20120607163830.GA13873@redhat.com> (raw)

The following changes since commit 8cc9b43f7c5f826b39af4b012ad89bb55faac29c:

  target-microblaze: lwx/swx: first implementation (2012-06-04 10:19:46 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git tags/for_anthony

for you to fetch changes up to 11e02c393109508fde4d99650f003dd2d6029bc5:

  pci_bridge_dev: fix error path in pci_bridge_dev_initfn() (2012-06-07 17:19:01 +0300)

----------------------------------------------------------------
rtl8139,pci,msi

This pull includes a bugfix for rtl8139 (this is independent of
Jason Wang's fix which Anthony has merged) and pci bridge hotplug bugfixes.
Further there are MSI/MSIX fixes and changes by Jan which should
also help merging device assignment down the road.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

----------------------------------------------------------------
Fernando Luis Vazquez Cao (1):
      rtl8139: honor RxOverflow flag in can_receive method

Jan Kiszka (9):
      ahci: Fix reset of MSI function
      intel-hda: Fix reset of MSI function
      ahci: Clean up reset functions
      msi: Guard msi_reset with msi_present
      msi: Invoke msi/msix_reset from PCI core
      msi: Guard msi/msix_write_config with msi_present
      msi: Invoke msi/msix_write_config from PCI core
      msi: Use msi/msix_present more consistently
      msix: Drop unused msix_bar_size

Jason Baron (2):
      qdev: release parent properties on dc->init failure
      pci_bridge_dev: fix error path in pci_bridge_dev_initfn()

Michael S. Tsirkin (1):
      shpc: unparent device before free

 hw/ide/ahci.c           | 25 +++++++++++++++----------
 hw/ide/ahci.h           |  2 +-
 hw/ide/ich.c            | 19 ++++++++-----------
 hw/intel-hda.c          | 12 ------------
 hw/ioh3420.c            |  3 +--
 hw/ivshmem.c            |  1 -
 hw/msi.c                | 11 ++++++++---
 hw/msix.c               | 23 +++++++++--------------
 hw/msix.h               |  2 --
 hw/pci.c                |  8 ++++++++
 hw/pci.h                |  2 --
 hw/pci_bridge.c         | 10 ++--------
 hw/pci_bridge_dev.c     |  8 ++++----
 hw/qdev.c               |  1 +
 hw/rtl8139.c            |  2 +-
 hw/shpc.c               |  1 +
 hw/virtio-pci.c         |  3 ---
 hw/xio3130_downstream.c |  3 +--
 hw/xio3130_upstream.c   |  3 +--
 19 files changed, 61 insertions(+), 78 deletions(-)

             reply	other threads:[~2012-06-07 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 16:38 Michael S. Tsirkin [this message]
2012-06-11 17:16 ` [Qemu-devel] [PULL] rtl8139,pci,msi Anthony Liguori
2012-06-11 17:22   ` Jan Kiszka
2012-06-11 20:01     ` Michael S. Tsirkin
2012-06-11 18:07   ` 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=20120607163830.GA13873@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=fernando@oss.ntt.co.jp \
    --cc=jan.kiszka@siemens.com \
    --cc=jbaron@redhat.com \
    --cc=kakuta.hayato@oss.ntt.co.jp \
    --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 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.