From: Gerd Hoffmann <kraxel@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: allen.m.kay@intel.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC PATCH v3 0/9] vfio: capability chains, sparse mmap, device specific regions, IGD support
Date: Tue, 01 Mar 2016 15:49:26 +0100 [thread overview]
Message-ID: <1456843766.23994.107.camel@redhat.com> (raw)
In-Reply-To: <20160216211249.13529.7276.stgit@gimli.home>
On Di, 2016-02-16 at 14:31 -0700, Alex Williamson wrote:
> v3:
Have a new version of this?
Want look at this, but it doesn't apply to qemu master.
thanks,
Gerd
next prev parent reply other threads:[~2016-03-01 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 21:31 [Qemu-devel] [RFC PATCH v3 0/9] vfio: capability chains, sparse mmap, device specific regions, IGD support Alex Williamson
2016-02-16 21:31 ` [Qemu-devel] [RFC PATCH v3 1/9] vfio: Add sysfsdev property for pci & platform Alex Williamson
2016-02-16 21:32 ` [Qemu-devel] [RFC PATCH v3 2/9] vfio: Wrap VFIO_DEVICE_GET_REGION_INFO Alex Williamson
2016-02-16 21:32 ` [Qemu-devel] [RFC PATCH v3 3/9] vfio: Generalize region support Alex Williamson
2016-02-16 21:32 ` [Qemu-devel] [RFC PATCH v3 4/9] vfio/pci: Convert all MemoryRegion to dynamic alloc and consistent functions Alex Williamson
2016-02-16 21:32 ` [Qemu-devel] [RFC PATCH v3 5/9] linux-headers/vfio: Update for proposed capabilities list Alex Williamson
2016-02-16 21:32 ` [Qemu-devel] [RFC PATCH v3 6/9] vfio: Enable sparse mmap capability Alex Williamson
2016-02-16 21:32 ` [Qemu-devel] [RFC PATCH v3 7/9] vfio/pci: Fixup PCI option ROMs Alex Williamson
2016-02-16 21:32 ` [Qemu-devel] [RFC PATCH v3 8/9] vfio/pci: Split out VGA setup Alex Williamson
2016-02-16 21:32 ` [Qemu-devel] [RFC PATCH v3 9/9] Intel IGD support for vfio Alex Williamson
2016-02-17 11:16 ` [Qemu-devel] [RFC PATCH v3 0/9] vfio: capability chains, sparse mmap, device specific regions, IGD support Tian, Kevin
2016-02-17 14:02 ` Alex Williamson
2016-03-01 14:49 ` Gerd Hoffmann [this message]
2016-03-01 15:29 ` Eric Auger
2016-03-01 20:21 ` Alex Williamson
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=1456843766.23994.107.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=allen.m.kay@intel.com \
--cc=kvm@vger.kernel.org \
--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).