2018-02-09 20:41+1100, Paul Mackerras: > Paolo or Radim, > > Please do a pull from my kvm-ppc-next-4.16-2 tag to get some PPC KVM > fixes that I would like to have go into 4.16. Most of them are quite > self-contained; there are two that are larger (and arguably don't > quite count as bug fixes), but I have checked them carefully and > convinced myself that they have a low risk of causing regressions, and > they do address issues that have been found in testing, so I put them > in. > > With things like this I would normally put them in my kvm-ppc-fixes > branch and base it on current upstream. However, as far as I can see > the kvm next branch hasn't been merged upstream yet. Therefore I made > this series a continuation of my kvm-ppc-next branch. I have resolved the resulting conflict and pulled, thanks. > When do you expect that kvm/next will get merged upstream? Hopefully on Sunday, sorry for the delay. -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
