[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2cdc7a3e-d516-70d5-9bfb-d077d40b07ed@redhat.com>
Date: Thu, 2 Apr 2020 10:15:01 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>, KVM <kvm@...r.kernel.org>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Haiwei Li <lihaiwei.kernel@...il.com>,
Tom Lendacky <thomas.lendacky@....com>,
Joerg Roedel <jroedel@...e.de>
Subject: Re: linux-next: manual merge of the kvm tree with Linus' tree
On 02/04/20 04:36, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the kvm tree got a conflict in:
>
> arch/x86/kvm/svm/svm.c
>
> between commits:
>
> aaca21007ba1 ("KVM: SVM: Fix the svm vmexit code for WRMSR")
> 2da1ed62d55c ("KVM: SVM: document KVM_MEM_ENCRYPT_OP, let userspace detect if SEV is available")
> 2e2409afe5f0 ("KVM: SVM: Issue WBINVD after deactivating an SEV guest")
>
> from Linus' tree and commits:
>
> 83a2c705f002 ("kVM SVM: Move SVM related files to own sub-directory")
> 41f08f0506c0 ("KVM: SVM: Move SEV code to separate file")
>
> (at least)
>
> from the kvm tree.
>
> Its a bit of a pain this code movement appearing during the merge
> window. Is it really intended for v5.7?
Yes, it's just due to code movement (a file was split, which I left last
to avoid pain for contributors and minimal room for regressions).
Unfortunately, git ends up being confused, but "git merge -X histogram"
actually does the right thing.
Paolo
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists