Re: [GIT PULL] Second batch of KVM changes for Linux 4.15

2017-11-27 Thread Linus Torvalds
On Mon, Nov 27, 2017 at 2:35 AM, Paolo Bonzini wrote: > > They came from the submaintainers' tree, so technically it wasn't in *my* > linux-next tree; if you looked at "linux-next as of the kvm/linux-next merge", > you wouldn't have found them. But they were not rebased at

Re: [GIT PULL] Second batch of KVM changes for Linux 4.15

2017-11-27 Thread Linus Torvalds
On Mon, Nov 27, 2017 at 2:35 AM, Paolo Bonzini wrote: > > They came from the submaintainers' tree, so technically it wasn't in *my* > linux-next tree; if you looked at "linux-next as of the kvm/linux-next merge", > you wouldn't have found them. But they were not rebased at least between >

Re: [GIT PULL] Second batch of KVM changes for Linux 4.15

2017-11-27 Thread Paolo Bonzini
On 25/11/2017 02:59, Linus Torvalds wrote: > > > On Nov 23, 2017 23:36, "Paolo Bonzini" > wrote: > > On 24/11/2017 04:50, Linus Torvalds wrote: > > > > So I pulled it, but then checked, > > > > None of this was in linux-next

Re: [GIT PULL] Second batch of KVM changes for Linux 4.15

2017-11-27 Thread Paolo Bonzini
On 25/11/2017 02:59, Linus Torvalds wrote: > > > On Nov 23, 2017 23:36, "Paolo Bonzini" > wrote: > > On 24/11/2017 04:50, Linus Torvalds wrote: > > > > So I pulled it, but then checked, > > > > None of this was in linux-next 20171117 either, >

Re: [GIT PULL] Second batch of KVM changes for Linux 4.15

2017-11-24 Thread Paolo Bonzini
On 24/11/2017 04:50, Linus Torvalds wrote: > On Mon, Nov 20, 2017 at 2:06 PM, Paolo Bonzini wrote: >> >> I am not including the host side of AMD SEV, because it wouldn't have gotten >> enough time in linux-next even with a "regular-length" merge window. It >> will be in

Re: [GIT PULL] Second batch of KVM changes for Linux 4.15

2017-11-24 Thread Paolo Bonzini
On 24/11/2017 04:50, Linus Torvalds wrote: > On Mon, Nov 20, 2017 at 2:06 PM, Paolo Bonzini wrote: >> >> I am not including the host side of AMD SEV, because it wouldn't have gotten >> enough time in linux-next even with a "regular-length" merge window. It >> will be in 4.16. > > So I pulled

Re: [GIT PULL] Second batch of KVM changes for Linux 4.15

2017-11-23 Thread Linus Torvalds
On Mon, Nov 20, 2017 at 2:06 PM, Paolo Bonzini wrote: > > I am not including the host side of AMD SEV, because it wouldn't have gotten > enough time in linux-next even with a "regular-length" merge window. It > will be in 4.16. So I pulled it, but then checked, None of

Re: [GIT PULL] Second batch of KVM changes for Linux 4.15

2017-11-23 Thread Linus Torvalds
On Mon, Nov 20, 2017 at 2:06 PM, Paolo Bonzini wrote: > > I am not including the host side of AMD SEV, because it wouldn't have gotten > enough time in linux-next even with a "regular-length" merge window. It > will be in 4.16. So I pulled it, but then checked, None of this was in linux-next

[GIT PULL] Second batch of KVM changes for Linux 4.15

2017-11-20 Thread Paolo Bonzini
Linus, The following changes since commit cf9b0772f2e410645fece13b749bd56505b998b8: Merge tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2017-11-16 16:05:01 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/virt/kvm/kvm.git

[GIT PULL] Second batch of KVM changes for Linux 4.15

2017-11-20 Thread Paolo Bonzini
Linus, The following changes since commit cf9b0772f2e410645fece13b749bd56505b998b8: Merge tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2017-11-16 16:05:01 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/virt/kvm/kvm.git