From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [GIT PULL] VFIO updates for v5.6-rc1
Date: Mon, 3 Feb 2020 13:40:37 -0700 [thread overview]
Message-ID: <20200203134037.2fda624f@w520.home> (raw)
Hi Linus,
The following changes since commit c79f46a282390e0f5b306007bf7b11a46d529538:
Linux 5.5-rc5 (2020-01-05 14:23:27 -0800)
are available in the Git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v5.6-rc1
for you to fetch changes up to 7b5372ba04ca1caabed1470d4ec23001cde2eb91:
vfio: platform: fix __iomem in vfio_platform_amdxgbe.c (2020-01-09 11:32:14 -0700)
----------------------------------------------------------------
VFIO updates for v5.6-rc1
- Fix nvlink error path (Alexey Kardashevskiy)
- Update nvlink and spapr to use mmgrab() (Julia Lawall)
- Update static declaration (Ben Dooks)
- Annotate __iomem to fix sparse warnings (Ben Dooks)
----------------------------------------------------------------
Alexey Kardashevskiy (1):
vfio/spapr/nvlink2: Skip unpinning pages on error exit
Ben Dooks (Codethink) (2):
vfio/mdev: make create attribute static
vfio: platform: fix __iomem in vfio_platform_amdxgbe.c
Julia Lawall (2):
vfio: vfio_pci_nvlink2: use mmgrab
vfio/spapr_tce: use mmgrab
drivers/vfio/mdev/mdev_sysfs.c | 2 +-
drivers/vfio/pci/vfio_pci_nvlink2.c | 8 +++++---
drivers/vfio/platform/reset/vfio_platform_amdxgbe.c | 4 ++--
drivers/vfio/vfio_iommu_spapr_tce.c | 2 +-
4 files changed, 9 insertions(+), 7 deletions(-)
next reply other threads:[~2020-02-03 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 20:40 Alex Williamson [this message]
2020-02-03 22:35 ` 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=20200203134037.2fda624f@w520.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
all inboxes | Powered by JetHome®