From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de ([212.227.17.10]:58061 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751912Ab1AIUco (ORCPT ); Sun, 9 Jan 2011 15:32:44 -0500 From: Arnd Bergmann Subject: Re: [PATCH 1/2] kbuild: asm-generic support Date: Sun, 9 Jan 2011 21:31:27 +0100 References: <20110108130302.GA21698@merkur.ravnborg.org> <20110109192707.GA12387@merkur.ravnborg.org> <20110109192907.GA12403@merkur.ravnborg.org> In-Reply-To: <20110109192907.GA12403@merkur.ravnborg.org> MIME-Version: 1.0 Message-Id: <201101092131.27694.arnd@arndb.de> Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Sam Ravnborg Cc: lkml , linux-kbuild , linux arch , Guan Xuetao , Michal Marek > There is an increasing amount of header files > shared between individual architectures in asm-generic. > To avoid a lot of dummy wrapper files that just > include the corresponding file in asm-generic provide > some basic support in kbuild for this. Looks almost perfect to me now. I was about to reply with Reviewed-by, but then it occurred to me that scripts/asm-generic.sh is really much more complicated than doing the same in Makefile syntax. You already create the wrapper files during headers-install, so why not also create them from make, where we already have access to the file lists in a convenient format. Or is there a problem getting at stuff defined in the Kbuild files from the prepare stage? Arnd