From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>,
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
Cc: "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 12:57:55 -0300 [thread overview]
Message-ID: <20210406155755.GA280925@nvidia.com> (raw)
In-Reply-To: <0-v3-225de1400dfc+4e074-vfio1_jgg@nvidia.com>
On Tue, Mar 23, 2021 at 01:14:52PM -0300, Jason Gunthorpe wrote:
> Jason Gunthorpe (14):
> vfio: Remove extra put/gets around vfio_device->group
> vfio: Simplify the lifetime logic for vfio_device
> vfio: Split creation of a vfio_device into init and register ops
> vfio/platform: Use vfio_init/register/unregister_group_dev
> vfio/fsl-mc: Re-order vfio_fsl_mc_probe()
> vfio/fsl-mc: Use vfio_init/register/unregister_group_dev
> vfio/pci: Move VGA and VF initialization to functions
> vfio/pci: Re-order vfio_pci_probe()
> vfio/pci: Use vfio_init/register/unregister_group_dev
> vfio/mdev: Use vfio_init/register/unregister_group_dev
> vfio/mdev: Make to_mdev_device() into a static inline
> vfio: Make vfio_device_ops pass a 'struct vfio_device *' instead of
> 'void *'
> vfio/pci: Replace uses of vfio_device_data() with container_of
> vfio: Remove device_data from the vfio bus driver API
Hi Alex,
Can you put this someplace to get zero day coverage? We are at rc6 now
Thanks,
Jason
next prev parent reply other threads:[~2021-04-06 15:57 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 ` Jason Gunthorpe [this message]
2021-04-06 19:38 ` [PATCH v3 00/14] Embed struct vfio_device in all sub-structures Alex Williamson
2021-04-06 19:45 ` Jason Gunthorpe
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=20210406155755.GA280925@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).