On Thu, Sep 05, 2019 at 11:01:14PM +0000, Dexuan Cui wrote:
This patchset (consisting of 9 patches) was part of the v4 patchset (consisting of 12 patches): https://lkml.org/lkml/2019/9/2/894 The other 3 patches in v4 are posted in another patchset, which will go through the tip.git tree. All the 9 patches here are now rebased to the hyperv tree's hyperv-next branch: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/log/?h=hyperv-next , and all the 9 patches have Michael Kelley's Signed-off-by's. Please review.
Given that these two series depend on each other, I'd much prefer for them to go through one tree. But, I may be wrong, and I'm going to see if a scenario such as this make sense. I've queued this one to the hyperv-next, but I'll wait for the x86 folks to send their pull request to Linus first before I do it for these patches. Usually cases such as these are the exception, but for Hyper-V it seems to be the norm, so I'm curious to see how this will unfold. -- Thanks, Sasha
