From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org,
Matthew Rosato <mjrosato@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 0/4] Move vfio_ccw to the new mdev API
Date: Thu, 28 Oct 2021 12:40:28 -0600 [thread overview]
Message-ID: <20211028124028.791050f3.alex.williamson@redhat.com> (raw)
In-Reply-To: <0-v4-cea4f5bd2c00+b52-ccw_mdev_jgg@nvidia.com>
On Tue, 26 Oct 2021 14:57:29 -0300
Jason Gunthorpe <jgg@nvidia.com> wrote:
> This is the first 4 patches of the v3 series which only change CCW to use
> the new VFIO API for mdevs and leaves the lifetime model as-is.
>
> As agreed, we will go ahead with this set and IBM can take the remaining
> patches of cleanup when they want. (I won't resend them)
>
> Alex: as Eric has now ack'd them please take them to the VFIO tree for
> this upcoming merge window
Applied to vfio next branch for v5.16. Thanks,
Alex
prev parent reply other threads:[~2021-10-28 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 17:57 [PATCH v4 0/4] Move vfio_ccw to the new mdev API Jason Gunthorpe
2021-10-26 17:57 ` [PATCH v4 1/4] vfio/ccw: Remove unneeded GFP_DMA Jason Gunthorpe
2021-10-26 17:57 ` [PATCH v4 2/4] vfio/ccw: Use functions for alloc/free of the vfio_ccw_private Jason Gunthorpe
2021-10-26 17:57 ` [PATCH v4 3/4] vfio/ccw: Pass vfio_ccw_private not mdev_device to various functions Jason Gunthorpe
2021-10-26 17:57 ` [PATCH v4 4/4] vfio/ccw: Convert to use vfio_register_emulated_iommu_dev() Jason Gunthorpe
2021-10-28 18:40 ` 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=20211028124028.791050f3.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=jgg@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=vneethv@linux.ibm.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