From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753839AbcK1D4x (ORCPT ); Sun, 27 Nov 2016 22:56:53 -0500 Received: from ozlabs.org ([103.22.144.67]:49791 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752302AbcK1D4n (ORCPT ); Sun, 27 Nov 2016 22:56:43 -0500 Date: Mon, 28 Nov 2016 14:56:41 +1100 From: Stephen Rothwell To: Marcelo Tosatti , Gleb Natapov , KVM , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Andy Lutomirski , Luwei Kang , Radim =?UTF-8?B?S3LEjW3DocWZ?= Subject: linux-next: manual merge of the kvm tree with the tip tree Message-ID: <20161128145641.24d1cd60@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, Today's linux-next merge of the kvm tree got a conflict in: arch/x86/kvm/cpuid.c between commit: c592b5734706 ("x86/fpu: Remove use_eager_fpu()") from the tip tree and commit: 4504b5c9414c ("kvm: x86: Add AVX512_4VNNIW and AVX512_4FMAPS support") from the kvm tree. I fixed it up (see below) and can carry the fix as necessary. This is now fixed as far as linux-next is concerned, but any non trivial conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc arch/x86/kvm/cpuid.c index 0aefb626fa8f,25f0f15fab1a..000000000000 --- a/arch/x86/kvm/cpuid.c +++ b/arch/x86/kvm/cpuid.c @@@ -16,6 -16,8 +16,7 @@@ #include #include #include + #include -#include /* For use_eager_fpu. Ugh! */ #include #include #include "cpuid.h"