linux-kernel - Re: [PATCH 2/4] [RFC] ARM: mass move of mach-*/plat-* header files

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201208221537.53904.arnd@arndb.de>
Date:	Wed, 22 Aug 2012 15:37:53 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Nicolas Pitre <nicolas.pitre@...aro.org>
Cc:	linux-arm-kernel@...ts.infradead.org,
	linaro-kernel@...ts.linaro.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] [RFC] ARM: mass move of mach-*/plat-* header files

On Wednesday 22 August 2012, Nicolas Pitre wrote:
> Ideally, files such as ...
> 
> > rename from arch/arm/mach-at91/include/mach/at91_pio.h
> > rename to arch/arm/mach-at91/include/mach-at91/at91_pio.h
> 
> should move next to the A91 GPIO driver file.  but that require manual 
> operations which can be done later.

Right. There are cases where we have to do this eventually because the
files are duplicated, e.g. at91/avr32, pxa/mmp, s3c/s5p/exynos, or
sa1100/pxa.

For the majority of cases where it's desirable to move the header file
closer to the driver, it's not actually a prerequisite to do this
in order to get a complete multiplatform setup.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/