From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [GIT PULL] VFIO updates for v5.2-rc1
Date: Fri, 10 May 2019 15:50:57 -0600 [thread overview]
Message-ID: <20190510155057.75cc97ba@x1.home> (raw)
Hi Linus,
The following changes since commit 085b7755808aa11f78ab9377257e1dad2e6fa4bb:
Linux 5.1-rc6 (2019-04-21 10:45:57 -0700)
are available in the Git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v5.2-rc1
for you to fetch changes up to 15c80c1659f27364734a3938b04d1c67479aa11c:
vfio: Add Cornelia Huck as reviewer (2019-05-08 11:41:26 -0600)
----------------------------------------------------------------
VFIO updates for v5.2-rc1
- Improve dev_printk() usage (Bjorn Helgaas)
- Fix issue with blocking in !TASK_RUNNING state while waiting for
userspace to release devices (Farhan Ali)
- Fix error path cleanup in nvlink setup (Greg Kurz)
- mdev-core cleanups and fixes in preparation for more use cases
(Parav Pandit)
- Cornelia has volunteered as an official vfio reviewer (Cornelia Huck)
----------------------------------------------------------------
Bjorn Helgaas (1):
vfio: Use dev_printk() when possible
Cornelia Huck (1):
vfio: Add Cornelia Huck as reviewer
Farhan Ali (1):
vfio: Fix WARNING "do not call blocking ops when !TASK_RUNNING"
Greg Kurz (1):
vfio-pci/nvlink2: Fix potential VMA leak
Parav Pandit (7):
vfio/mdev: Avoid release parent reference during error path
vfio/mdev: Removed unused kref
vfio/mdev: Drop redundant extern for exported symbols
vfio/mdev: Avoid masking error code to EBUSY
vfio/mdev: Follow correct remove sequence
vfio/mdev: Fix aborting mdev child device removal if one fails
vfio/mdev: Avoid inline get and put parent helpers
MAINTAINERS | 1 +
drivers/vfio/mdev/mdev_core.c | 18 +++----
drivers/vfio/mdev/mdev_private.h | 1 -
drivers/vfio/mdev/mdev_sysfs.c | 2 +-
drivers/vfio/pci/vfio_pci.c | 23 ++++-----
drivers/vfio/pci/vfio_pci_config.c | 29 +++++------
drivers/vfio/pci/vfio_pci_nvlink2.c | 2 +
.../vfio/platform/reset/vfio_platform_amdxgbe.c | 5 +-
drivers/vfio/platform/vfio_platform_common.c | 12 +++--
drivers/vfio/vfio.c | 59 +++++++++-------------
include/linux/mdev.h | 21 ++++----
include/linux/pci.h | 3 ++
12 files changed, 81 insertions(+), 95 deletions(-)
next reply other threads:[~2019-05-10 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 21:50 Alex Williamson [this message]
2019-05-11 15:00 ` [GIT PULL] VFIO updates for v5.2-rc1 pr-tracker-bot
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=20190510155057.75cc97ba@x1.home \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--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 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).