On Wed, Jan 20, 2021, Kai Huang wrote: > I'd like to take this chance to ask: when this series is ready to be merged, what is > the properly way to merge? This series has x86 non-sgx (cpufeature, feat_ctl) and sgx > changes, and it obviously has KVM changes too. So instance, who should be the one to > take this series? And which tree and branch should I rebase to in next version? The path of least resistance is likely to get acks for the x86 and sgx changes, and let Paolo take it through the KVM tree. The KVM changes are much more likely to have non-trivial conflicts, e.g. making exit_reason a union touches a ton of code; getting and carrying acked-by for those will be tough sledding.
