On 4/13/22 12:33 PM, Jani Nikula wrote: > On Mon, 11 Apr 2022, Christoph Hellwig <hch@xxxxxx> wrote: >> On Mon, Apr 11, 2022 at 07:11:03PM +0300, Jani Nikula wrote: >>>> Up to you but I usually sort these lists >>> >>> Yeah, please do. Otherwise matches what I sent, so ack. >> >> Let's just merge your 2 patch series ASAP and I'll rebase on top of >> that. > > I rebased them on top of current gvt-next and resent [1]. Zhenyu, Zhi, > please pick them up if you approve. > >> What branch in drm-intel should I use as the base for the next version >> btw? Or does gvt go through yet another tree? > > It's yet another tree... Basically gvt is developed on top of gvt-next > (see MAINTAINERS) and Zhenyu and Zhi send pull requests for > drm-intel-next. > Hi Jani and Christoph: It seems Jani's makefile clean patch has already included this one, I can just simply drop this one so that Christoph won't need to re-send everything. For the branch to move on, I am merging the patches and will re-generate the gvt-staging branch, which combines the newest drm-tip vfio-upstream and other gvt branches. If you are in a rush of re-basing the patches of non-GVT-g stuff, you can use gvt-staging branch until my pull request landed in drm-intel-next. Also our QA will test gvt-staging-branch before the pull request. I suppose it will take one or two days. Again, thanks so much for making this happen. Thanks, Zhi. > > BR, > Jani. > > > [1] https://lore.kernel.org/all/cover.1649852517.git.jani.nikula@xxxxxxxxx >
