Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Arnd Bergmann <arnd@kernel.org>,
	intel-gfx@lists.freedesktop.org,
	intel-gvt-dev@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915/gvt: Move mdev attribute groups into kvmgt module
Date: Thu, 13 May 2021 12:56:47 +0800	[thread overview]
Message-ID: <20210513045647.GQ4589@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <20210512124739.GC1096940@ziepe.ca>


[-- Attachment #1.1: Type: text/plain, Size: 730 bytes --]

On 2021.05.12 09:47:39 -0300, Jason Gunthorpe wrote:
> On Wed, May 12, 2021 at 10:31:41AM +0800, Zhenyu Wang wrote:
> 
> > > This need to go into the vfio tree in some way, either directly
> > > through it, via rc or otherwise
> > 
> > As this is only for i915/gvt, once drm/i915 backmerge with linus master,
> > it should still go through normal i915/gvt merge path.
> 
> Don't do this, you will create conflicts with ongoing vfio work.
> 

Sure, there always could be conflict, which means you need to rebase onto
this cleanup. Would that a problem? I'd want to fix current workaround
in 5.13-rc.  Merging i915/gvt only change through vfio doesn't make sense
to me, I will handle that instead of Alex.

Thanks

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2021-05-13  5:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11  8:33 [Intel-gfx] [PATCH 0/3] Fix I915_GVT dependency Zhenyu Wang
2021-05-11  8:33 ` [Intel-gfx] [PATCH 1/3] drm/i915/gvt: Move mdev attribute groups into kvmgt module Zhenyu Wang
     [not found]   ` <20210511155446.GB1096940@ziepe.ca>
2021-05-12  2:31     ` Zhenyu Wang
     [not found]       ` <20210512124739.GC1096940@ziepe.ca>
2021-05-13  4:56         ` Zhenyu Wang [this message]
     [not found]           ` <20210513120249.GH1096940@ziepe.ca>
2021-05-14  7:08             ` Zhenyu Wang
2021-05-13  8:39   ` [Intel-gfx] [PATCH v2] " Zhenyu Wang
2021-05-17  6:45     ` Colin Xu
2021-05-11  8:33 ` [Intel-gfx] [PATCH 2/3] Revert "vfio/gvt: fix DRM_I915_GVT dependency on VFIO_MDEV" Zhenyu Wang
2021-05-17  6:45   ` Colin Xu
2021-05-11  8:33 ` [Intel-gfx] [PATCH 3/3] Revert "vfio/gvt: Make DRM_I915_GVT depend " Zhenyu Wang
2021-05-17  6:46   ` Colin Xu
2021-05-11  8:34 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Fix I915_GVT dependency Patchwork
2021-05-13  9:20 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Fix I915_GVT dependency (rev2) Patchwork

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=20210513045647.GQ4589@zhen-hp.sh.intel.com \
    --to=zhenyuw@linux.intel.com \
    --cc=arnd@kernel.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=jgg@ziepe.ca \
    /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