On 10/11/2016 9:21 AM, Alex Williamson wrote: > On Tue, 11 Oct 2016 01:58:32 +0530 > Kirti Wankhede <kwankhede@xxxxxxxxxx> wrote: >> --- >> drivers/vfio/Kconfig | 1 + >> drivers/vfio/Makefile | 1 + >> drivers/vfio/mdev/Kconfig | 12 ++ >> drivers/vfio/mdev/Makefile | 5 + >> drivers/vfio/mdev/mdev_core.c | 363 +++++++++++++++++++++++++++++++++++++++ >> drivers/vfio/mdev/mdev_driver.c | 131 ++++++++++++++ >> drivers/vfio/mdev/mdev_private.h | 41 +++++ >> drivers/vfio/mdev/mdev_sysfs.c | 295 +++++++++++++++++++++++++++++++ >> include/linux/mdev.h | 178 +++++++++++++++++++ >> 9 files changed, 1027 insertions(+) >> create mode 100644 drivers/vfio/mdev/Kconfig >> create mode 100644 drivers/vfio/mdev/Makefile >> create mode 100644 drivers/vfio/mdev/mdev_core.c >> create mode 100644 drivers/vfio/mdev/mdev_driver.c >> create mode 100644 drivers/vfio/mdev/mdev_private.h >> create mode 100644 drivers/vfio/mdev/mdev_sysfs.c >> create mode 100644 include/linux/mdev.h > > > Overall this is heading in a good direction. What kernel is this > series against? I could only apply it to v4.7, yet some of the > dependencies claimed in the cover letter are only in v4.8. linux-next > or v4.8 are both good baselines right now, as we move to v4.9-rc > releases, linux-next probably becomes a better target. > Thanks Alex. Yes, this series is against kernel v4.7. Patch 1 - 5 gets applied to linux-next cleanly, patch 6/6 shows conflicts against linux-next. I'm preparing next version of this patch set against linux-next. Thanks, Kirti. > A few initial comments below, I'll likely have more as I wrap my head > around it. Thanks, > > Alex > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
