Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752800AbdHJPMK (ORCPT ); Thu, 10 Aug 2017 11:12:10 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:32853 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752133AbdHJPMJ (ORCPT ); Thu, 10 Aug 2017 11:12:09 -0400 Date: Thu, 10 Aug 2017 17:12:05 +0200 From: Ingo Molnar To: Vitaly Kuznetsov Cc: Thomas Gleixner , Ingo Molnar , Greg Kroah-Hartman , devel@linuxdriverproject.org, linux-kernel@vger.kernel.org, "K. Y. Srinivasan" , Haiyang Zhang , Stephen Hemminger , "H. Peter Anvin" , Steven Rostedt , Jork Loeser , Simon Xiao , Andy Lutomirski , Andy Shevchenko , x86@kernel.org Subject: Re: [PATCH v10 0/9] Hyper-V: paravirtualized remote TLB flushing and hypercall improvements Message-ID: <20170810151205.mtvhkrgyjnacsmef@gmail.com> References: <20170802160921.21791-1-vkuznets@redhat.com> <87k22btz0v.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87k22btz0v.fsf@vitty.brq.redhat.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1297 Lines: 32 * Vitaly Kuznetsov wrote: > Vitaly Kuznetsov writes: > > > Changes since v9: > > - Rebase to 4.13-rc3. > > - Drop PATCH1 as it was already taken by Greg to char-misc tree. There're no > > functional dependencies on this patch so the series can go through a different tree > > (and it actually belongs to x86 if I got Ingo's comment right). > > - Add in missing void return type in PATCH1 [Colin King, Ingo Molnar, Greg KH] > > - A few minor fixes in what is now PATCH7: add pr_fmt, tiny style fix in > > hyperv_flush_tlb_others() [Andy Shevchenko] > > - Fix "error: implicit declaration of function 'virt_to_phys'" in PATCH2 > > reported by kbuild test robot (#include ) > > - Add Steven's 'Reviewed-by:' to PATCH9. > > Thomas, Ingo, Greg, > > do I get it right that the intention is to take this series through x86 > tree? (See: https://www.spinics.net/lists/kernel/msg2561174.html) If so, > is there anything else I need to do to get it accepted? Yeah, the patches are arch/x86/-heavy, so that would be the ideal workflow - it's just that the series coincided with x86 maintainers vacation time! I've picked them up now into tip:x86/platform (they look good to me) and will push them out after some testing. Thanks, Ingo