Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932316AbcDVRml (ORCPT ); Fri, 22 Apr 2016 13:42:41 -0400 Received: from mout.kundenserver.de ([217.72.192.73]:53086 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752461AbcDVRmj (ORCPT ); Fri, 22 Apr 2016 13:42:39 -0400 From: Arnd Bergmann To: Catalin Marinas Cc: Yury Norov , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, pinskia@gmail.com, Prasun.Kapoor@caviumnetworks.com, schwab@suse.de, broonie@kernel.org, linux-doc@vger.kernel.org, heiko.carstens@de.ibm.com, agraf@suse.de, klimov.linux@gmail.com, bamvor.zhangjian@huawei.com, schwidefsky@de.ibm.com, Nathan_Lynch@mentor.com, joseph@codesourcery.com, christoph.muellner@theobroma-systems.com Subject: Re: [PATCH 18/25] arm64: ilp32: introduce binfmt_ilp32.c Date: Fri, 22 Apr 2016 19:41:28 +0200 Message-ID: <5122105.YDc1h2V3NP@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20160422165130.GQ2998@e104818-lin.cambridge.arm.com> References: <1459894127-17698-1-git-send-email-ynorov@caviumnetworks.com> <1459894127-17698-19-git-send-email-ynorov@caviumnetworks.com> <20160422165130.GQ2998@e104818-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:C7272TEMyBxEhNKpEVayEP2D6FGd8mg8GniWVLZ0XhEMUMoAnwP 9Q15vSCR6+jTfkYeIBLr/HO8gYb5bVxFvC3lD/BgorJQZe5N0zCfmLrILFSdyood6Qth1ZK ixuRdTF0pFxTiHOZFdtvz19l8gEGwb+7Yvd6mgcBRuttPEl1FBiQxNb4Mydc4XJBSj8YIit 1Rc7L7SUrpmzQ4PQRTjiA== X-UI-Out-Filterresults: notjunk:1;V01:K0:LBfcWb57+lI=:/rqxvHd63R4B+Zxnfi9w3l xrAr0hmt57JGq9MmvX95q4iXUXrxTY8qdjyI7JeBlqlk4l60qEFlM7upjmxoYFqeW4weTAcC6 Yes8/Ly9QixCVdImYNh67QljPmDNiCGpmwSSOXCha4IhK/Zf069bYymcjxRCIH4qxpFzyfl97 x9JvT9sU2J5mzZIvRylewH4i1wZCYQ8qj16pZ8svQKeyxwuimhLry1yIZX7IOjS8nH1GAYkei kWB/wTnkquM3rC/xaVJ3vKOP69SoFljmaEmU/Zv4hZKpebvqA6ANs7GFHj9czR59fmLyd0qCR O3uNQUVikQezQJXSAXCWHFQMDwJCSl5/xHckr8x0FpdW3vNf/EAaFqV9fA9MP7jdkOKLLrthw SHzgUbVAHcP4Ct+8zji8K3q0CC9j4rPXpRsh1JtK+1fzlLtgcRXNIHVy7Rw4OiDtZDtW+u270 fSwnFz0OnStI2oPYLQB4S6xDtB+1IwK1viZZVGjb2tkcU9ndeAs1JVaqf4zallrWZVrWKwvVT yTsY2txLsa/lhopLzTe4gxJYa8HHPcsyYlur7UsYUh3ZH7xdALsOVLc/Q4EVW1GS6Ym7BswPp b8Db4yBV5GFN24DbmKjUFOCy5JII2K+DJPD06eNqtmmO1psOkdEcRHwJPj3xLDvVxlFscl2Yv 2S7b/lr8rBO83r8csqSCVvMblrmlO7m8RnvGShs06yfhgMg66MzckqidIiPZe6EULaD0gjwzV lQYrKDX9RkRO1gKR Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1051 Lines: 26 On Friday 22 April 2016 17:51:30 Catalin Marinas wrote: > On Wed, Apr 06, 2016 at 01:08:40AM +0300, Yury Norov wrote: > > --- /dev/null > > +++ b/arch/arm64/kernel/binfmt_ilp32.c > > [...] > > > +#include "../../../fs/binfmt_elf.c" > > How different is this new binfmt_ilp32.c file from the first part of > compat_binfmt_elf.c? I wonder whether we could include the latter here > instead and make this similar to binfmt_elf32.c introduced by the > previous patch. That is how the earlier versions did it, and I thought it ended up too ugly with lots of runtime checks instead of compile-time checks. The current version is how I asked it to be done. A slight variation would be to keep using fs/compat_binfmt_elf.c for one of the two compat modes (today it is used for aarch32) and have a separate file include "../../../fs/binfmt_elf.c" for the other mode (as this patch does for ilp32). I think that is what I asked for, but there was probably a good reason for having two files in the same directory. The result is basically the same. Arnd