All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Yi Liu <yi.l.liu@intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	yi.y.sun@linux.intel.com, kevin.tian@intel.com,
	cohuck@redhat.com, eric.auger@redhat.com, nicolinc@nvidia.com,
	kvm@vger.kernel.org, mjrosato@linux.ibm.com,
	chao.p.peng@linux.intel.com
Subject: Re: [PATCH 00/10] Move group specific code into group.c
Date: Mon, 5 Dec 2022 09:43:43 -0400	[thread overview]
Message-ID: <Y431j8HBvuCsvP+U@nvidia.com> (raw)
In-Reply-To: <fecfc22d-cb9e-cac9-95ff-21df13f257c2@intel.com>

On Sat, Dec 03, 2022 at 09:53:18PM +0800, Yi Liu wrote:

> > > Please rebase it on the above branch also
> 
> To Jason: done. Please fetch from below branch.
> 
> https://github.com/yiliu1765/iommufd/commits/for-jason/vfio_group_split

Okay, it is merged in to the iommufd tree

> > It looks fine to me aside from the previous review comments and my own
> > spelling nit.  I also don't see that this adds any additional conflicts
> > vs the existing iommufd integration for any outstanding vfio patches on
> > the list, therefore, where there's not already a sign-off from me:
> > 
> > Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
> 
> To Alex: thanks. above branch is based on Jason's for-next. So may have
> one minor conflict with below commit in your next branch.
> 
> vfio: Remove vfio_free_device

It seems OK, I did a test merge

Thanks,
Jason

  reply	other threads:[~2022-12-05 13:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 14:55 [PATCH 00/10] Move group specific code into group.c Yi Liu
2022-12-01 14:55 ` [PATCH 01/10] vfio: Simplify vfio_create_group() Yi Liu
2022-12-01 14:55 ` [PATCH 02/10] vfio: Move the sanity check of the group to vfio_create_group() Yi Liu
2022-12-01 14:55 ` [PATCH 03/10] vfio: Create wrappers for group register/unregister Yi Liu
2022-12-01 14:55 ` [PATCH 04/10] vfio: Set device->group in helper function Yi Liu
2022-12-02  5:34   ` Tian, Kevin
2022-12-01 14:55 ` [PATCH 05/10] vfio: Swap order of vfio_device_container_register() and open_device() Yi Liu
2022-12-01 14:55 ` [PATCH 06/10] vfio: Move device open/close code to be helpfers Yi Liu
2022-12-02  5:44   ` Tian, Kevin
2022-12-02  6:37     ` Yi Liu
2022-12-01 14:55 ` [PATCH 07/10] vfio: Refactor vfio_device open and close Yi Liu
2022-12-02  6:15   ` Tian, Kevin
2022-12-02  6:37     ` Yi Liu
2022-12-02 15:07       ` Jason Gunthorpe
2022-12-02 21:58   ` Alex Williamson
2022-12-03 13:46     ` Yi Liu
2022-12-01 14:55 ` [PATCH 08/10] vfio: Wrap vfio group module init/clean code into helpers Yi Liu
2022-12-01 14:55 ` [PATCH 09/10] vfio: Refactor dma APIs for emulated devices Yi Liu
2022-12-01 14:55 ` [PATCH 10/10] vfio: Move vfio group specific code into group.c Yi Liu
2022-12-02  6:26   ` Tian, Kevin
2022-12-01 20:39 ` [PATCH 00/10] Move " Jason Gunthorpe
2022-12-02 13:57   ` Yi Liu
2022-12-02 14:44     ` Jason Gunthorpe
2022-12-02 23:12       ` Alex Williamson
2022-12-03 13:53         ` Yi Liu
2022-12-05 13:43           ` Jason Gunthorpe [this message]
2022-12-06  7:31           ` Yang, Lixiao
2022-12-07  4:12             ` He, Yu

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=Y431j8HBvuCsvP+U@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=cohuck@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=nicolinc@nvidia.com \
    --cc=yi.l.liu@intel.com \
    --cc=yi.y.sun@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.