RFC ARM: start to move SoC code into arch/arm/mach-*
Get series with b4
b4 am 20150204135216.GA9304@amdVersions newest first
- v1 RFC Latest1 of 21 patches 0 repliesNew
1 of 21 patches is in this archive. The cover letter announces 21.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 4/21 | ARM: tegra: collect SoC sources into mach-tegra | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [RFC PATCH 0/21] ARM: start to move SoC code into arch/arm/mach-*
Quoted 23 lines · Stephen Warren
Quoted 11 lines · Simon Glass
Hi Albert,
Quoted 8 lines · Albert ARIBAUD
Hello Masahiro,
Quoted 3 lines · Masahiro Yamada
This series can be applied on the current u-boot/master (commit
37b608a52dcb133)Quoted 7 lines
Quoted 3 lines
I'd rather not have all mach-* directories just below
arch/arm/. Can't they be created underarch/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...this is what the kernel does and it does seem convenient.
Do note that
arch/arm/mach*doesn't/won't entirely match what the Linux kernel does.
Quoted 8 lines
In Linux,
arch/arm64doesn't have mach-* sub-directories, and the arm/arm64 architectures are different so don't share the code inarch/arm/mach-tegra, so there's work underway to move stuff out ofarch/arm/mach-tegraand into either appropriate subsystem directories ordrivers/soc/tegra.Given all that, I suspect we should decide the directory layout of U-Boot based on what's best for U-Boot, not by trying to chase the changing target of the Linux kernel.
Well, I'd say that best directory layout is the one we are familiar with ... from Linux. And we don't need to chase that target.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html