[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170826072404.ocjypnhp2b5rnh4l@gmail.com>
Date: Sat, 26 Aug 2017 09:24:04 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: 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>,
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
* Paolo Bonzini <pbonzini@...hat.com> wrote:
> 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.
I've merged it to tip:x86/mm where the SME bits live and will propagate it to
linux-next ASAP, once it's gone through my local testing.
Thanks,
Ingo
Powered by blists - more mailing lists