[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87373nt2fd.fsf@vitty.brq.redhat.com>
Date: Wed, 03 Jan 2018 15:57:58 +0100
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>
Cc: Paolo Bonzini <pbonzini@...hat.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
kvm@...r.kernel.org,
Radim Krčmář
<rkrcmar@...hat.com>, Haiyang Zhang <haiyangz@...rosoft.com>,
x86@...nel.org, linux-kernel@...r.kernel.org,
"Michael Kelley \(EOSG\)" <Michael.H.Kelley@...rosoft.com>,
Roman Kagan <rkagan@...tuozzo.com>,
Andy Lutomirski <luto@...nel.org>,
devel@...uxdriverproject.org, Mohammed Gamal <mmorsy@...hat.com>
Subject: Re: [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V
Vitaly Kuznetsov <vkuznets@...hat.com> writes:
> Paolo Bonzini <pbonzini@...hat.com> writes:
>>
>> Patches 5-7 are
>>
>> Acked-by: Paolo Bonzini <pbonzini@...hat.com>
>>
>> I would appreciate if the Hyper-V folks can provide a topic branch to be
>> merged in both HV and KVM trees.
>>
>
> There's no such thing as Hyper-V tree, patches are usually getting
> merged through 'tip' tree when the majority of changes go to arch/x86 or
> Greg's char-misc tree when changes are drivers/hv heavy (+ net, scsi,
> pci, hid, ... trees for individual drivers).
>
> In this particular case the series is x86-heavy and I believe it should
> go through x86 'tip' tree.
>
> Thomas, Ingo, Peter, could you please take a look? Thanks!
Gentle ping after the holidays season :-)
--
Vitaly
Powered by blists - more mailing lists