All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	virtualization@lists.linux-foundation.org,
	Anthony Liguori <anthony@codemonkey.ws>,
	kvm@vger.kernel.org, avi@redhat.com, Carsten Otte <
Subject: [PATCH 0/2] virtio: device removal fixes
Date: Tue, 21 Jul 2009 18:58:13 +0300	[thread overview]
Message-ID: <20090721155813.GA3306@redhat.com> (raw)

Here are a couple of obviously correct fixes for virtio device removal.
Since these fix regressions (for devices with msi-x capability), I think
we need them for 2.6.31.  Sorry about the late notice.

Michael S. Tsirkin (2):
  virtio: fix memory leak on device removal
  virtio: fix double free_irq

 drivers/virtio/virtio_pci.c |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)

             reply	other threads:[~2009-07-21 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 15:58 Michael S. Tsirkin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-21 15:58 [PATCH 0/2] virtio: device removal fixes 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=20090721155813.GA3306@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=kvm@vger.kernel.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 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.