From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL 0/3] VFIO fixes 2019-11-18
Date: Mon, 18 Nov 2019 11:46:25 -0700 [thread overview]
Message-ID: <157410270703.24655.9333886493163056872.stgit@gimli.home> (raw)
The following changes since commit 1bd0f1c9c149c2fb738f381099cec7ad0ee224a9:
Merge remote-tracking branch
'remotes/kraxel/tags/seabios-20191118-pull-request' into staging (2019-11-18
14:30:24 +0000)
are available in the Git repository at:
git://github.com/awilliam/qemu-vfio.git tags/vfio-fixes-20191118.0
for you to fetch changes up to 29b95c992a569818294478b4616e44b45c67d34e:
vfio: vfio-pci requires EDID (2019-11-18 10:41:49 -0700)
----------------------------------------------------------------
VFIO fixes 2019-11-18
- Fix migration blocker double free (Michal Privoznik)
- Use migration_add_blocker() return value (Jens Freimann)
- Depend on EDID for display support (Paolo Bonzini)
----------------------------------------------------------------
Jens Freimann (1):
vfio: don't ignore return value of migrate_add_blocker
Michal Privoznik (1):
hw/vfio/pci: Fix double free of migration_blocker
Paolo Bonzini (1):
vfio: vfio-pci requires EDID
hw/vfio/Kconfig | 1 +
hw/vfio/pci.c | 4 +++-
2 files changed, 4 insertions(+), 1 deletion(-)
next reply other threads:[~2019-11-18 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 18:46 Alex Williamson [this message]
2019-11-18 18:46 ` [PULL 1/3] hw/vfio/pci: Fix double free of migration_blocker Alex Williamson
2019-11-18 18:46 ` [PULL 2/3] vfio: don't ignore return value of migrate_add_blocker Alex Williamson
2019-11-18 18:47 ` [PULL 3/3] vfio: vfio-pci requires EDID Alex Williamson
2019-11-19 9:17 ` [PULL 0/3] VFIO fixes 2019-11-18 Peter Maydell
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=157410270703.24655.9333886493163056872.stgit@gimli.home \
--to=alex.williamson@redhat.com \
--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).