[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <575d1d5a-5cfb-49b4-0ce7-b78372739cb6@redhat.com>
Date: Fri, 25 Aug 2017 22:42:54 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Brijesh Singh <brijesh.singh@....com>,
Tom Lendacky <thomas.lendacky@....com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Radim Krčmář <rkrcmar@...hat.com>,
KVM <kvm@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Yu Zhang <yu.c.zhang@...ux.intel.com>, paolo.bonzini@...il.com
Subject: Re: linux-next: manual merge of the kvm tree with the tip tree
On 25/08/2017 22:41, Brijesh Singh wrote:
>>>>
>
>> Neither my version nor yours is correct. :) The right one has [0][i]
>> and [1][i] (I inverted the indices by mistake).
>>
>> With that change, you can include my
>>
>> Acked-by: Paolo Bonzini <pbonzini@...hat.com>
>>
>
> Ingo,
>
> I assuming that this patch should be sent through the tip since SME support
> came from tip. I will be submitting the patch very soon.
Yes, that is correct. I cannot apply it directly to the KVM tree.
Paolo
Powered by blists - more mailing lists