On 09/11/2016 03:03, Zhenyu Wang wrote: > On 2016.11.07 10:17:54 +0100, Daniel Vetter wrote: >>>> Paolo, for this case, do you think it's feasible we pick them through >>>> drm/i915 merge path? As currently initial KVMGT patch sets require these >>>> exported symbols, that's why I ask how we should handle this dependency. >>> >>> Then it's actually a good thing that I dropped from kvm/queue! You can >>> certainly include these patches, but please do that through a topic branch. >>> >>> I've prepared a branch for you >>> (git://git.kernel.org/pub/scm/virt/kvm/kvm.git branch for-kvmgt). Once >>> Linus processes my outstanding pull request, the branch will only >>> include the three page-tracking patches. Please pull that topic branch >>> into your own branch, and ensure you have a merge commit when you send >>> the pull request to Daniel. The merge commit ensures that the workflow >>> was correct; use --no-ff if necessary. >>> >>> You can do the same for Jike's patches for the KVM-VFIO device, when >>> Alex reviews them, and I suppose you'll need a topic branch for mdev >>> too? I didn't know that KVMGT was planned for 4.10. In the future, >>> let's synchronize ahead so that we can prepare topic branches for you. >> >> Ok, back from the useless wifi at plumbers, I can mail again. Zhenyu >> confirmed on irc that the initial code pile only needs this. For the >> cross-maintainer topic tree I prefer a formal pull request with stable >> tag. Please also cc: intel-gfx on that, since I plan to merge that one >> directly into i915. >> > > Paolo, could you help to do this for Daniel? Daniel would like to merge > current KVMGT required change for KVM directly, then I'd base KVMGT change > on that. Yes, I'll send it today. Paolo
Attachment:
signature.asc
Description: OpenPGP digital signature
