From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Diana Craciun <diana.craciun@oss.nxp.com>,
Eric Auger <eric.auger@redhat.com>,
kvm@vger.kernel.org, Kirti Wankhede <kwankhede@nvidia.com>,
linux-doc@vger.kernel.org, "Raj, Ashok" <ashok.raj@intel.com>,
Bharat Bhushan <Bharat.Bhushan@nxp.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Dan Williams <dan.j.williams@intel.com>,
Daniel Vetter <daniel@ffwll.ch>, Christoph Hellwig <hch@lst.de>,
Jike Song <jike.song@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Leon Romanovsky <leonro@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
Tarun Gupta <targupta@nvidia.com>, Liu Yi L <yi.l.liu@intel.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Zhi Wang <zhi.a.wang@intel.com>
Subject: Re: [PATCH v3 00/14] Embed struct vfio_device in all sub-structures
Date: Tue, 6 Apr 2021 16:45:44 -0300 [thread overview]
Message-ID: <20210406194544.GF282464@nvidia.com> (raw)
In-Reply-To: <20210406133815.40cc1503@omen>
On Tue, Apr 06, 2021 at 01:38:15PM -0600, Alex Williamson wrote:
> On Tue, 23 Mar 2021 13:14:52 -0300
> Jason Gunthorpe <jgg@nvidia.com> wrote:
> >
> > Documentation/driver-api/vfio.rst | 48 ++--
> > drivers/vfio/fsl-mc/vfio_fsl_mc.c | 127 +++++----
> > drivers/vfio/fsl-mc/vfio_fsl_mc_private.h | 1 +
> > drivers/vfio/mdev/mdev_private.h | 5 +-
> > drivers/vfio/mdev/vfio_mdev.c | 53 ++--
> > drivers/vfio/pci/vfio_pci.c | 253 ++++++++++--------
> > drivers/vfio/pci/vfio_pci_private.h | 1 +
> > drivers/vfio/platform/vfio_amba.c | 8 +-
> > drivers/vfio/platform/vfio_platform.c | 20 +-
> > drivers/vfio/platform/vfio_platform_common.c | 56 ++--
> > drivers/vfio/platform/vfio_platform_private.h | 5 +-
> > drivers/vfio/vfio.c | 210 +++++----------
> > include/linux/vfio.h | 37 ++-
> > 13 files changed, 417 insertions(+), 407 deletions(-)
>
>
> Applied to vfio next branch for v5.13. Thanks!
Thanks! I just sent v2 of the mdev one, there was not much to revise
there, it should be good if there are no comments in the next days.
I have to polish the 'create fails' workflow on the vfio_mdev.c
removal series then I will post it. Not sure I can make this cycle.
Jason
prev parent reply other threads:[~2021-04-06 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 16:14 [PATCH v3 00/14] Embed struct vfio_device in all sub-structures Jason Gunthorpe
2021-03-23 16:14 ` [PATCH v3 03/14] vfio: Split creation of a vfio_device into init and register ops Jason Gunthorpe
2021-03-23 16:15 ` [PATCH v3 12/14] vfio: Make vfio_device_ops pass a 'struct vfio_device *' instead of 'void *' Jason Gunthorpe
2021-03-23 16:15 ` [PATCH v3 14/14] vfio: Remove device_data from the vfio bus driver API Jason Gunthorpe
2021-04-06 15:57 ` [PATCH v3 00/14] Embed struct vfio_device in all sub-structures Jason Gunthorpe
2021-04-06 19:38 ` Alex Williamson
2021-04-06 19:45 ` Jason Gunthorpe [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=20210406194544.GF282464@nvidia.com \
--to=jgg@nvidia.com \
--cc=Bharat.Bhushan@nxp.com \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=cohuck@redhat.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=daniel@ffwll.ch \
--cc=diana.craciun@oss.nxp.com \
--cc=eric.auger@redhat.com \
--cc=hch@lst.de \
--cc=jike.song@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=targupta@nvidia.com \
--cc=yi.l.liu@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.com \
/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).