qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/8] VFIO updates 2016-03-10
Date: Thu, 10 Mar 2016 21:16:03 -0700	[thread overview]
Message-ID: <20160310211603.15a9ba7d@t450s.home> (raw)
In-Reply-To: <CAFEAcA-xZanqSa7huNBD9p+CpKTFrB34DBCfOQ+BG5QX6nG1PA@mail.gmail.com>

On Fri, 11 Mar 2016 08:24:51 +0700
Peter Maydell <peter.maydell@linaro.org> wrote:

> On 10 March 2016 at 23:55, Alex Williamson <alex.williamson@redhat.com> wrote:
> > The following changes since commit a648c137383d84bc4f95696e5293978d9541a26e:
> >
> >   Merge remote-tracking branch 'remotes/kraxel/tags/pull-ui-20160309-1' into staging (2016-03-10 02:51:14 +0000)
> >
> > are available in the git repository at:
> >
> >
> >   git://github.com/awilliam/qemu-vfio.git tags/vfio-update-20160310.1
> >
> > for you to fetch changes up to f953b1a565c9fa0551c5023056c28fbbe35c8b9d:
> >
> >   MAINTAINERS: Add entry for the include/hw/vfio/ folder (2016-03-10 09:39:09 -0700)
> >
> > ----------------------------------------------------------------
> > VFIO updates 2016-03-10
> >
> >  - Allow devices to be specified via sysfs path (Alex Williamson)
> >  - vfio region helpers and generalization for future device specific regions
> >    (Alex Williamson)
> >  - Automatic ROM device ID and checksum fixup (Alex Williamson)
> >  - Split VGA setup to allow enabling VGA from quirks (Alex Williamson)
> >  - Remove fixed string limit for ROM MemoryRegion name (Neo Jia)
> >  - MAINTAINERS update (Thomas Huth)  
> 
> This fails to build on OSX and Windows:
> 
> In file included from /Users/pm215/src/qemu-for-merges/hw/arm/sysbus-fdt.c:35:
> In file included from
> /Users/pm215/src/qemu-for-merges/include/hw/vfio/vfio-platform.h:20:
> /Users/pm215/src/qemu-for-merges/include/hw/vfio/vfio-common.h:28:10:
> fatal error: 'linux/vfio.h' file
>       not found
> #include <linux/vfio.h>
>          ^

Gack, guess I'll wrap that in CONFIG_LINUX like is already done in
sysbus-fdt.c.  Sorry again.  Thanks,

Alex

      reply	other threads:[~2016-03-11  4:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 16:55 [Qemu-devel] [PULL 0/8] VFIO updates 2016-03-10 Alex Williamson
2016-03-10 16:55 ` [Qemu-devel] [PULL 1/8] vfio: Add sysfsdev property for pci & platform Alex Williamson
2016-03-10 16:55 ` [Qemu-devel] [PULL 2/8] vfio: Wrap VFIO_DEVICE_GET_REGION_INFO Alex Williamson
2016-03-10 16:55 ` [Qemu-devel] [PULL 3/8] vfio: Generalize region support Alex Williamson
2016-03-10 16:55 ` [Qemu-devel] [PULL 4/8] vfio/pci: Convert all MemoryRegion to dynamic alloc and consistent functions Alex Williamson
2016-03-10 16:55 ` [Qemu-devel] [PULL 5/8] vfio/pci: Fixup PCI option ROMs Alex Williamson
2016-03-10 16:55 ` [Qemu-devel] [PULL 6/8] vfio/pci: Split out VGA setup Alex Williamson
2016-03-10 16:56 ` [Qemu-devel] [PULL 7/8] vfio/pci: replace fixed string limit by g_strdup_printf Alex Williamson
2016-03-10 16:56 ` [Qemu-devel] [PULL 8/8] MAINTAINERS: Add entry for the include/hw/vfio/ folder Alex Williamson
2016-03-11  1:24 ` [Qemu-devel] [PULL 0/8] VFIO updates 2016-03-10 Peter Maydell
2016-03-11  4:16   ` Alex Williamson [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=20160310211603.15a9ba7d@t450s.home \
    --to=alex.williamson@redhat.com \
    --cc=peter.maydell@linaro.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).