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.3-rc1
Date: Tue, 16 Jul 2019 09:18:15 -0600 [thread overview]
Message-ID: <20190716091815.74662138@x1.home> (raw)
Hi Linus,
The following changes since commit 6fbc7275c7a9ba97877050335f290341a1fd8dbf:
Linux 5.2-rc7 (2019-06-30 11:25:36 +0800)
are available in the Git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-v5.3-rc1
for you to fetch changes up to 1e4d09d2212d9e230b967f57bc8df463527dbd75:
mdev: Send uevents around parent device registration (2019-07-11 13:26:52 -0600)
----------------------------------------------------------------
VFIO updates for v5.3-rc1
- Static symbol cleanup in mdev samples (Kefeng Wang)
- Use vma help in nvlink code (Peng Hao)
- Remove unused code in mbochs sample (YueHaibing)
- Send uevents around mdev registration (Alex Williamson)
----------------------------------------------------------------
Alex Williamson (1):
mdev: Send uevents around parent device registration
Kefeng Wang (1):
vfio-mdev/samples: make some symbols static
Peng Hao (1):
vfio: vfio_pci_nvlink2: use a vma helper function
YueHaibing (1):
sample/mdev/mbochs: remove set but not used variable 'mdev_state'
drivers/vfio/mdev/mdev_core.c | 9 +++++++
drivers/vfio/pci/vfio_pci_nvlink2.c | 3 +--
samples/vfio-mdev/mbochs.c | 3 ---
samples/vfio-mdev/mtty.c | 47 +++++++++++++++++++------------------
4 files changed, 34 insertions(+), 28 deletions(-)
next reply other threads:[~2019-07-16 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 15:18 Alex Williamson [this message]
2019-07-17 18:30 ` [GIT PULL] VFIO updates for v5.3-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=20190716091815.74662138@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