From: Peter Maydell <peter.maydell@linaro.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/3] VFIO updates 2017-10-03
Date: Thu, 5 Oct 2017 14:43:03 +0100 [thread overview]
Message-ID: <CAFEAcA9Xxpv_t29Udd8NPxJQa5NCv7FDMeFJ6xH6XYreNikFmg@mail.gmail.com> (raw)
In-Reply-To: <20171003221012.17156.23559.stgit@gimli.home>
On 3 October 2017 at 23:12, Alex Williamson <alex.williamson@redhat.com> wrote:
> The following changes since commit d147f7e815f97cb477e223586bcb80c316ae10ea:
>
> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2017-10-03 16:27:24 +0100)
>
> are available in the git repository at:
>
>
> git://github.com/awilliam/qemu-vfio.git tags/vfio-updates-20171003.0
>
> for you to fetch changes up to dfbee78db8fdf7bc8c151c3d29504bb47438480b:
>
> vfio/pci: Add NVIDIA GPUDirect Cliques support (2017-10-03 12:57:36 -0600)
>
> ----------------------------------------------------------------
> VFIO updates 2017-10-03
>
> - NVIDIA GPUDirect Cliques experimental support (Alex Williamson)
>
> ----------------------------------------------------------------
> Alex Williamson (3):
> vfio/pci: Do not unwind on error
> vfio/pci: Add virtual capabilities quirk infrastructure
> vfio/pci: Add NVIDIA GPUDirect Cliques support
>
Applied, thanks.
-- PMM
prev parent reply other threads:[~2017-10-05 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 22:12 [Qemu-devel] [PULL 0/3] VFIO updates 2017-10-03 Alex Williamson
2017-10-03 22:12 ` [Qemu-devel] [PULL 1/3] vfio/pci: Do not unwind on error Alex Williamson
2017-10-03 22:12 ` [Qemu-devel] [PULL 2/3] vfio/pci: Add virtual capabilities quirk infrastructure Alex Williamson
2017-10-03 22:13 ` [Qemu-devel] [PULL 3/3] vfio/pci: Add NVIDIA GPUDirect Cliques support Alex Williamson
2017-10-05 13:43 ` Peter Maydell [this message]
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=CAFEAcA9Xxpv_t29Udd8NPxJQa5NCv7FDMeFJ6xH6XYreNikFmg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=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).