From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932479AbbKMLil (ORCPT ); Fri, 13 Nov 2015 06:38:41 -0500 Received: from mail-wm0-f53.google.com ([74.125.82.53]:33157 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754650AbbKMLik (ORCPT ); Fri, 13 Nov 2015 06:38:40 -0500 Date: Fri, 13 Nov 2015 12:38:43 +0100 From: Christoffer Dall To: Arnd Bergmann Cc: Marc Zyngier , Catalin Marinas , Will Deacon , linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ARM64: use linux/types.h in kvm.h Message-ID: <20151113113843.GG12968@cbox> References: <9679324.UdV9GV0mFA@wuerfel> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9679324.UdV9GV0mFA@wuerfel> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 12, 2015 at 03:41:08PM +0100, Arnd Bergmann wrote: > We should always use linux/types.h instead of asm/types.h for > consistency, and Kbuild actually warns about it: > > ./usr/include/asm/kvm.h:35: include of is preferred over > > This patch does as Kbuild asks us. > > Signed-off-by: Arnd Bergmann I don't see this error when building the kernel, does it require a special option to check for these things? In any case, thanks for the patch, I have applied it. -Christoffer From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoffer Dall Subject: Re: [PATCH] ARM64: use linux/types.h in kvm.h Date: Fri, 13 Nov 2015 12:38:43 +0100 Message-ID: <20151113113843.GG12968@cbox> References: <9679324.UdV9GV0mFA@wuerfel> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 464F549630 for ; Fri, 13 Nov 2015 06:38:23 -0500 (EST) Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n1023v-Ks55S for ; Fri, 13 Nov 2015 06:38:22 -0500 (EST) Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) by mm01.cs.columbia.edu (Postfix) with ESMTPS id 34A7D41280 for ; Fri, 13 Nov 2015 06:38:22 -0500 (EST) Received: by wmdw130 with SMTP id w130so25224452wmd.0 for ; Fri, 13 Nov 2015 03:38:38 -0800 (PST) Content-Disposition: inline In-Reply-To: <9679324.UdV9GV0mFA@wuerfel> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu To: Arnd Bergmann Cc: Marc Zyngier , Catalin Marinas , Will Deacon , linux-kernel@vger.kernel.org, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org List-Id: kvmarm@lists.cs.columbia.edu On Thu, Nov 12, 2015 at 03:41:08PM +0100, Arnd Bergmann wrote: > We should always use linux/types.h instead of asm/types.h for > consistency, and Kbuild actually warns about it: > > ./usr/include/asm/kvm.h:35: include of is preferred over > > This patch does as Kbuild asks us. > > Signed-off-by: Arnd Bergmann I don't see this error when building the kernel, does it require a special option to check for these things? In any case, thanks for the patch, I have applied it. -Christoffer From mboxrd@z Thu Jan 1 00:00:00 1970 From: christoffer.dall@linaro.org (Christoffer Dall) Date: Fri, 13 Nov 2015 12:38:43 +0100 Subject: [PATCH] ARM64: use linux/types.h in kvm.h In-Reply-To: <9679324.UdV9GV0mFA@wuerfel> References: <9679324.UdV9GV0mFA@wuerfel> Message-ID: <20151113113843.GG12968@cbox> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Nov 12, 2015 at 03:41:08PM +0100, Arnd Bergmann wrote: > We should always use linux/types.h instead of asm/types.h for > consistency, and Kbuild actually warns about it: > > ./usr/include/asm/kvm.h:35: include of is preferred over > > This patch does as Kbuild asks us. > > Signed-off-by: Arnd Bergmann I don't see this error when building the kernel, does it require a special option to check for these things? In any case, thanks for the patch, I have applied it. -Christoffer