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 fixes for v5.13-rc5
Date: Thu, 3 Jun 2021 11:22:37 -0600 [thread overview]
Message-ID: <20210603112237.42b620c1.alex.williamson@redhat.com> (raw)
Hi Linus,
The following changes since commit d07f6ca923ea0927a1024dfccafc5b53b61cfecc:
Linux 5.13-rc2 (2021-05-16 15:27:44 -0700)
are available in the Git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v5.13-rc5
for you to fetch changes up to dc51ff91cf2d1e9a2d941da483602f71d4a51472:
vfio/platform: fix module_put call in error flow (2021-05-24 13:40:13 -0600)
----------------------------------------------------------------
VFIO fixes for v5.13-rc5
- Fix error path return value (Zhen Lei)
- Add vfio-pci CONFIG_MMU dependency (Randy Dunlap)
- Replace open coding with struct_size() (Gustavo A. R. Silva)
- Fix sample driver error path (Wei Yongjun)
- Fix vfio-platform error path module_put() (Max Gurtovoy)
----------------------------------------------------------------
Gustavo A. R. Silva (1):
vfio/iommu_type1: Use struct_size() for kzalloc()
Max Gurtovoy (1):
vfio/platform: fix module_put call in error flow
Randy Dunlap (1):
vfio/pci: zap_vma_ptes() needs MMU
Wei Yongjun (1):
samples: vfio-mdev: fix error handing in mdpy_fb_probe()
Zhen Lei (1):
vfio/pci: Fix error return code in vfio_ecap_init()
drivers/vfio/pci/Kconfig | 1 +
drivers/vfio/pci/vfio_pci_config.c | 2 +-
drivers/vfio/platform/vfio_platform_common.c | 2 +-
drivers/vfio/vfio_iommu_type1.c | 2 +-
samples/vfio-mdev/mdpy-fb.c | 13 +++++++++----
5 files changed, 13 insertions(+), 7 deletions(-)
next reply other threads:[~2021-06-03 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 17:22 Alex Williamson [this message]
2021-06-03 19:09 ` 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=20210603112237.42b620c1.alex.williamson@redhat.com \
--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®