From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Wang, Zhi A" <zhi.a.wang@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
Christoph Hellwig <hch@lst.de>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Zhenyu Wang <zhenyuw@linux.intel.com>
Subject: Re: [PULL v2] gvt-next
Date: Wed, 20 Apr 2022 17:00:34 -0300 [thread overview]
Message-ID: <20220420200034.GE2120790@nvidia.com> (raw)
In-Reply-To: <20220420174600.GD2120790@nvidia.com>
On Wed, Apr 20, 2022 at 02:46:00PM -0300, Jason Gunthorpe wrote:
> On Wed, Apr 20, 2022 at 11:40:33AM -0600, Alex Williamson wrote:
> > On Wed, 20 Apr 2022 13:43:51 -0300
> > Jason Gunthorpe <jgg@nvidia.com> wrote:
> >
> > > On Wed, Apr 20, 2022 at 04:34:47PM +0000, Wang, Zhi A wrote:
> > > > Hi folks:
> > > >
> > > > Here is the PR of gvt-next. Thanks so much for the patience.
> > > >
> > > > Mostly it includes the patch bundle of GVT-g re-factor patches for adapting the GVT-g with the
> > > > new MDEV interfaces:
> > > >
> > > > - Separating the MMIO table from GVT-g. (Zhi)
> > > > - GVT-g re-factor. (Christoph)
> > > > - GVT-g mdev API cleanup. (Jason)
> > > > - GVT-g trace/makefile cleanup. (Jani)
> > > >
> > > > Thanks so much for making this happen.
> > > >
> > > > This PR has been tested as following and no problem shows up:
> > > >
> > > > $dim update-branches
> > > > $dim apply-pull drm-intel-next < this_email.eml
> > > >
> > > > The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
> > > >
> > > > Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > > https://github.com/intel/gvt-linux tags/gvt-next-2022-04-20-for-christoph
> > > >
> > > > for you to fetch changes up to ae7875879b7c838bffb42ed6db4658e5c504032e:
> > > >
> > > > vfio/mdev: Remove mdev drvdata (2022-04-20 03:15:58 -0400)
> > >
> > > This looks well constructed now! thanks
> > >
> > > Alex you can pull this for VFIO after Jani&co grab it
> > >
> > > I'll respin my vfio_group series on top of this branch
> >
> > Sure, so just to confirm tags/gvt-next-2022-04-20-for-christoph is
> > pruned down to exactly the commits we're looking for now? Thanks,
>
> Yes, the above is correct and the tag points to commit
> ae7875879b7c838bffb42ed6db4658e5c504032e
>
> It is the bare minimum series
Actually this topic branch doesn't compile:
../drivers/gpu/drm/i915/intel_gvt_mmio_table.c:7:10: fatal error: 'display/intel_dmc_regs.h' file not found
#include "display/intel_dmc_regs.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
:( :(
This is the merge conflict that was mentioned. This topic branch needs
to delete the above intel_dmc_regs.h include file
When drm-intel-next merges this PR then need to add it back as part of
the merge resolution - so explain this in the PR text above and
include a diff that does it when you send it again. (or do the merge
yourself as I showed before, it depends on what drm-intel-next wants)
Jason
next prev parent reply other threads:[~2022-04-20 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 16:34 [PULL v2] gvt-next Wang, Zhi A
2022-04-20 16:43 ` Jason Gunthorpe
2022-04-20 17:40 ` Alex Williamson
2022-04-20 17:46 ` Jason Gunthorpe
2022-04-20 20:00 ` Jason Gunthorpe [this message]
2022-04-21 4:57 ` Wang, Zhi A
2022-04-21 5:47 ` Christoph Hellwig
2022-04-21 6:41 ` Joonas Lahtinen
2022-04-21 13:14 ` Jason Gunthorpe
2022-04-21 14:13 ` Wang, Zhi A
-- strict thread matches above, loose matches on Subject: below --
2022-04-26 8:37 Wang, Zhi A
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=20220420200034.GE2120790@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@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