From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Sun, 1 Feb 2015 11:11:44 +0100 Subject: [U-Boot] [RFC PATCH 0/21] ARM: start to move SoC code into arch/arm/mach-* In-Reply-To: References: <1422166283-20822-1-git-send-email-yamada.m@jp.panasonic.com> <20150201040217.03b74a23@lilith> Message-ID: <20150201111144.3d30aa1a@lilith> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Simon, On Sat, 31 Jan 2015 20:20:06 -0700, Simon Glass wrote: > Hi Albert, > > On 31 January 2015 at 20:02, Albert ARIBAUD wrote: > > Hello Masahiro, > > > > On Sun, 25 Jan 2015 15:11:02 +0900, Masahiro Yamada > > wrote: > >> > >> This series can be applied on the current u-boot/master > >> (commit 37b608a52dcb133) > > > > I'd rather not have all mach-* directories just below arch/arm/. Can't > > they be created under arch/arm/soc/ instead? That would give a cleaner > > structure IMO. > > It does save a level and I am forever typing cpu/armv7 to get what > feels like nowhere... That can easily be solved (and tuned to personal taste) with CDPATH, eg. uboot at lilith:~/src/u-boot-arm (master)$ export CDPATH=arch/arm/cpu:arch/arm uboot at lilith:~/src/u-boot-arm (master)$ cd armv armv7/ armv8/ uboot at lilith:~/src/u-boot-arm (master)$ cd armv7 /home/uboot/src/u-boot-arm/arch/arm/cpu/armv7 uboot at lilith:~/src/u-boot-arm/arch/arm/cpu/armv7 (master)$ (the u-boot-friendly value of CDPATH can put in a u-boot_env.sh file to be sourced along with other u-boot related settings) > this is what the kernel does and it does seem convenient. Well, to me it does not really -- I'm ok with loads of mach-* subdirs under a commin parent dir, but what's the benefit of mixing mach-* dirs with non-mach-* ones? > Regards, > Simon Amicalement, -- Albert.