From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758278Ab2JKJ5m (ORCPT ); Thu, 11 Oct 2012 05:57:42 -0400 Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:64321 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758250Ab2JKJ5h (ORCPT ); Thu, 11 Oct 2012 05:57:37 -0400 Date: Thu, 11 Oct 2012 10:57:05 +0100 From: Will Deacon To: Geert Uytterhoeven Cc: David Howells , "torvalds@osdl.org" , "arnd@arndb.de" , "hpa@zytor.com" , Catalin Marinas , "linux-arch@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "ralf@linux-mips.org" , "ddaney.cavm@gmail.com" , Paul Mundt Subject: Re: Message-ID: <20121011095705.GB30598@mudshark.cambridge.arm.com> References: <22758.1349565339@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Sun, Oct 07, 2012 at 07:36:20AM +0100, Geert Uytterhoeven wrote: > On Sun, Oct 7, 2012 at 1:15 AM, David Howells wrote: > > (3) m68k turned out to have a header installation problem due to it lacking a > > kvm_para.h file. > > Sh also. and arm64 iirc. It should also affect arm, but we have a horrible dummy header to get around it (just includes the asm-generic variant). I posted a fix, but then it got derailed by the wildcarding used to generate generic headers for kvm (which I was going some way to removing): https://lkml.org/lkml/2012/8/2/173 http://marc.info/?l=linux-kernel&m=134393963216492&w=2 Will